Pricing in Delivery

Normally, we do not configure pricing in Delivery.

Pricing is normally copied from the Sales order to the Billing document and quantity is copied from the Delivery to the Billing document.

But, sometime we need the condition like "Postage cost", "Packing cost" etc during Delivery.

In that case, we assign the Delivery Pricing Procedure to the Delivery Type and create condition record for those condition types (ZV01, ZVPA etc.).

When you create Delivery, these condition will appear in the delivery document and during billing they copied to Billing Document.

RVAB01 - Tax included in Price

Standard Pricing procedure to handle Tax Inclusive price. - RVAB01

Serial number table

Get Serial number from Table for a Delivery

Give delivery number in SER01 (in LIEF_NR) and get OBKNR

Then put OBKNR in OBJK to get Serial number in SERNR

Partner functions ECC vs CRM

http://scn.sap.com/community/crm/master-data-and-middleware/blog/2013/09/03/partner-functions--what-how-and-where

Manual completion of delivery - VL_COMPLETE

VL_COMPLETE – Transaction to manually complete Deliveries.  Can be used instead of deleting deliveries. 

 

 

Storage Location Determination in Sales order

Storage Location determination is NOT standard in SAP.  It is done using customer exits in MV45AFZZ. Please see below link

 

https://scn.sap.com/thread/1532418

 

Also refer to SAP note 387482 - https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D33383734383226

Get Group from Outbound Delivery number - VBSS (Table)

VBSS table - Give delivery in VBELN, take Group from SAMMG

No standard transaction to achieve this.

Problem: If invoice created with wrong price

Problem: If invoice created with wrong price that involved production order

STEPS TO FOLLOW

1.       VF11 Cancel customer invoice

2.       Reverse GI in VL09

3.       Delete the delivery in VL02N

4.       Unbook the production OR in MIGO (102 mov.)

5.       Set the MAP (Moving average price) in MR21 (same value as sum of components)

6.       Update the pricing in the sales OR (cost)

7.       Book the production OR in MIGO (101 mov.)

8.       Do GI again in VL02N

9.       Invoice both lines together in VF01 (online)

10.   Fix the code

11.   Fix the product setup procedure (master data)

12.   Reverse the chargeback CHBK document

TAS free line

 

https://scn.sap.com/thread/1785713

 

 

OVAL transaction – To block Sales documents when customer has ‘Order block’

OVAL transaction – To block Sales documents when customer has 'Order block'.

 

 

Handling Units tcodes

 

Intercompany Scenario - Sales Process

 

 

Packing status in Delivery header

Packing status in Delivery header will be changed to 'C' (Completed) though there are some items with out packing.

This is standard behaviour if the item category is set to (in 0VLP) 'Can be packed' - As it is not necessary for all items to be Packed.

There is a different setting in 0VLP called 'must be packed' - you can use this if you want header to be Completed only if all items are must packed.

SAP note (KBA) - 1508233 

Block for Accounting - Posting block

SPRO config:

Billing Document type -> Posting block

 

 

 

Credit Management: Setup credit check for documents

VOV8 -> Check Credit limit

 

SPRO-> Sales and Distribution -> Basic Functions -> Credit Management ->

 

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

CHBK - Set to complete status manually - if not needed to go for CHBC

WLF2V tcode -> From Menu (Remuneration Settlement) -> Select 'Complete'.

Completed documents will not appear in WLFCOL tcode - > So, no CHBCs can be created on them

Trigger idoc on change of customer data

For the automatic transfer of master data ,we can use change pointer technique.

Following are the steps to be followed:-

1) Enable change pointer globally (t.code BD61).

 

2)Enable Change Pointers for a Message Type (t.code BD50).

Here you have to check the Active checkbox corresponding to customer master message type 'DEBMAS'.

 

3)Specify the Fields for Which Change Pointers Are to Be Written (t.code BD52).

Various number of fields are present here corresponding to message type'DEBMAS'. If you want to add any other field , you can add here.

 

Apart from above three settings, all other ALE configurations are required like( partner profile, distribution model etc.) Eg: SALE tcode, setup distribution model

 

For triggering the Idoc program 'RBDMIDOC' should be scheduled.

When you make any change in the customer master , Idoc will be triggered automatically from your SAP system.

Outputs tcodes

VOK2 - Maintain Output determination
NACE - Conditions of Output control

VV11	Create Output – Sales
VV12	Change Output – Sales
VV13	Display Output – Sales

VVG1	Create Output – Groups
VVG2	Change Output – Groups
VVG3	Display Output – Groups

VL06P - List of Outbound Dlvs for Picking Logistics Execution - Shipping

VP01SHP - Print parameter maintenance shipping SD - Output Determination

V/38 - Maintain Condition Type Appl V4 SD - Material Maintenance

OVLT - C SD Table TVST "Picking Lists" SD - Material Maintenance

VT07 - Collective run in background Logistics Execution - Transportation

V/53 - View V_TNAPR Appl. V4 SD - Conditions

 

VV21	Create Output – Shipping
VV22	Change Output – Shipping
VV23	Display Output – Shipping

VL71		Output from Deliveries
VL72		Output from Grouped Deliveries

VV31	Create Output – Billing
VV32	Change Output – Billing
VV33	Display Output – Billing

MN04	Create Message: - PO
MN05	Create Message: - PO
MN06	Create Message: - PO

Pick Lists
VP01SHP	Print parameter maintenance shipping	(Config) Create output for Shipping Point e.g. Pick Lists (This is config)
VOK2		(Config) Go to SD document > picking list > condition type
VG02		Change Picking Group

Production Order Pick Lists
OPK8	Names of Lists	( Config  Transaction) Config setup for the printing of production orders
OPKP	Production Scheduling Profile	(Config Transaction) Config setup for the printing of production orders
Material Document (Goods Receipt)
MN21	Create Output – Condition Records: Inventory Management	Create output to mail details of Goods Receipts to Sales / Purchaser. CMS Condition Types ZLGR (Receipt Buyer), ZSGR (Receipt Sales) ZCGR (Receipt Cancel Buyer) ZCSR (Receipt Cancel Sales)
MN22	Change Output – Condition Records: Inventory Management	Change output to mail details of Goods Receipts to Sales / Purchaser. CMS Condition Types ZLGR (Receipt Buyer), ZSGR (Receipt Sales)
MN23	Display Output – Condition Records: Inventory Management	Display output to mail details of Goods Receipts to Sales / Purchaser. CMS Condition Types ZLGR (Receipt Buyer), ZSGR (Receipt Sales)

 

Program	Notes
RV80HGEN	Program used to regenerate all VOFM routines. Can be used if the routine does not appear to be working. Needs to be run carefully as it could have an impact on the business if run during business hours.

Handling Units:
VL74 - Output from Handling units
VV63 - Display Ouput: Handling Units
 

Billing split to avoid 999 items issue in FI doc

Below link is useful:
http://scn.sap.com/thread/1519325

In IMG setting, you can restrict the number of line item that should flow in billing.

 

Go to IMG => SD => Billing => Billing Docs => Country specific features.
You also require to change copy routine for split (refer routine 006) to consider the limit given above.


Also, While creating invoice via VF01 you can go to selection list and choose the lines which you want to invoice.

Credit Management

OVA8 - Automated Credit control - You set up config for risk category - switch on/off checks

User exit for OVA8 'User1' - LVKMPFZ1

VKM3 - Release credit block for Sales orders
VKM4 - Release credit block for SD documents (Deliv etc)

FD32 - Customer credit management change - assign risk category etc..