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

[SAP EWM] Batch job to reprocess the failed queues in SMQ1 and SMQ2

Reports RSQOWKEX/RSQIWKEX can be scheduled as a periodic background job to reset the status of LUWs registered to outbound(SMQ1)/inbound(SMQ2) queues. RSQOWKEX for outbound queues (SMQS/SMQ1). RSQIWKEX for inbound queues (SMQR/SMQ2). The below parameters are to be maintained : Queue Name as '*' Select 'No Running Queues' Do not select 'No Retry queus' Queues running longer than  < Time in Mins > ideally 20 mins No queues older than < Data > Note that this job will change the status of the failed queue to 'READY' status so that scheduler will process it. But for any queues struck in 'READY' status, th ese need to be processed manually.
Post a Comment
Read more

[SAP SD] Mass deletion of deliveries in SAP

If there is the requirement for collective deletion of Outbound deliveries in standard, the following can be performed. Transaction VL10* with corresponding user role settings can meet this requirement. Go to VL10*, only flag indicator 'With Deliveries' in 'Data Selection' column in User Role After flagging above indicator, go into the following screen. Then flag indicator of 'Add to delivery', and fill the delivery numbers or other parameters into corresponding fields and then execute In the display screen, select the lines and click 'Delete' button
Post a Comment
Read more

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...
1 comment
Read more