Which of the following about Pricing Procedure Determination is correct

(a) Prices can be changed in the condition procedure of a sales document and these changes will be marked as “changed manually”
(b) Prices cannot be changed in the condition procedure of a sales document but you can add prices manually to a sales document
(c) You cannot prevent manual changes to condition types in the condition procedure of a sales document
(d) Header conditions can be entered manually at header level and is valid for all items
(e) Header conditions will be automatically distributed proportionally across the items based on net value. The basis of the distribution cannot be changed in the pricing procedure.

Answer thru your comments.

SD Jobs in UK

Release Strategy-Pricing

When we enter PR00 in the condition record VK11 , one of the options that we see is Material with Release strategy. What is this release strategy?

Pricing: Real Time Scenario

We need to create a custom table.
Field contents :
Routes, delivery priorities, transportation zones, and transportation planning point.
We have to create a table ZCustom with the above fields and add this field into the Field catalog.

Access Sequence would be
0001: Routes/deliverypriority
0002: tzone/Tpoint/route/delivery priority

Pricing Routine Requirements
A pricing routine is required to calculate the pricing condition value.
Routine -911: If a condition type Pr00 = 0 then move the condition value of PR01 into Pro0 . Both these condition types will use the above access sequence and both are Basic Prices.

Questions:
1 How would you proceed to add fields in the field catalog after creating the custom table
2 Where would you encapsulate the above routine i.e. in Alctype, Req or Cndbase value and against which condition type Proo or Pro1
Its a real time case scenario, please assist .

GAP Analysis

Gap analysis is the study of the differences between two different information systems or applications (ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.
Actual gap analysis is time consuming and it plays vital role in blue print stage.
The Gaps can differ from company to company. Most commonly, however, missing functionality is industry-specific.

Examples

In customer master data the client requirement needs legacy customer number which can be solved with User exit.
In sales order we need customer Phone number, we can use user exit
If client want new field in customer master like nearest fire station.

GAP analysis is done in Blue Print stage. It aims to understand what can be done with the standard SAP and how the client actually wants a particular scenario to be processed.
It’s an understanding of the GAP between the actual & required scenarios.

Tthe difference between agreed work and completed work is GAP Analysis.

E.g.: To Fill This Gap, We Use The Enhancements,These Enhancements Divided Into Exits, Like User exits, Field Exits Screen Exits & Menu Exits.These Enhancements are used to update the standard program in its Respective Business Transactions, Used as a Gateway to Meet the Client Requirements.

User Exits

Ways to find Enhancements/User exits

In SMOD find options of screen, menu, function exits.
Go to SE81 and select the relevant module find the enhancement.
Go to the program or transaction and search for “CALL CUSTOMER-FUCTION” or “EXIT__nnn”
For screen exits go to screen in SE51/SE80 search for- “CALL CUSTOMER-SUBSCREEN..”

User Exits & Customer Exits :

User Exits: These are subroutines used in the SAP namespace 'hard-coded' at various points within SAP Repository objects.

Customer Exits :

1. Menu Exits: Menu exits add items to the pull down menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications. These special entries have function codes that begin with "+" (a plus sign).

2. Screen Exits: Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special sub screen areas on a standard R/3 screen and calling a customer sub screen from the standard screen’s flow logic. It is called by call customer- sub screen

3.Function Module Exits :Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits. When you add a new menu item to a standard pulldown menu, you use a function module exit to define the actions that should take place once your menu is activated. Function module exits also control the data flow between standard programs and screen exit fields.
It is called by Call Customer- function

Some basic questions

1 In SO/Del/Billing we can enter material with different divisions (Config in VoV8), but can we enter materials with different distribution channels in a sales order and why we dont have this option ?

2 What is the difference between itemcatgory group and general item category group?

3 Under what business scenarios do we have to use condition types for both header and item level.