Skip to main content

16 steps of pricing procedure - SAP SD , MM

Below are the 16 steps of the pricing procedure :

Step  - It depicts condition type sequence similar to Sl.No

Counter - it's a substep 

Condition type - Pricing elements are represented as a condition type 

Description - this field displays description of the condition type

From, To   - From, and To  covers the Steps to be considered during condition value calculation 

Manual - if we select this, condition type should be manually entered in the document

Required - if we select this, the system will not allow you to save the document until it is entered

Statistical - if we select this, the Specific condition value doesn't have any impact during the price calculation

Print - if the specific condition type should be printed or not will be controlled in this field

SubTotal - It's used for temporary storage and can be subsequently used in other calculations

Alternate Calculation type - if the condition value should be derived based on a specific calculation and not through condition records then we will be maintain it

Alternate Condition Base Value - if the base value to be calculated based on other calculation then we have to go with this field

Account Key - this will be used to pass the  condition values of the specific condition type to the accounting 

Accruals - this is for provisional account posting 


Comments

Post a Comment

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).
4 comments
Read more

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.
Post a Comment
Read more

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...
1 comment
Read more