Skip to main content

Third Party process explained

In general, When the business receives an order from a customer and in return business transfer the order to the manufacturer such that OEM delivers goods directly to the customer.

This process is termed as third party process where goods will be directly dispatched to the customer.


Below are the trigger points :

1.Item Category - TAS with billing relevance as ' F' Order related billing with Invoice Quantity
2. Schedule line category - CS with account assignment category as '1' and Item Category '5'

Check P. Req Del. Sched if we require passing Sales order schedules to Purchase Requisition
3. Assign Order related Billing type at document type level.
4. Billing Quantity at Copy Control should be ' F'

Based on the above setting Purchase Requisition gets generated upon save of sales order.

As Account assignment category '1' is not relevant for goods receipt so upon Purchase order invoice document will be done.

Once vendor invoice is received then customer invoice will be generated.

If business requires Customer invoice to be generated upon Logical GR then account assignment category should be maintained as ' Sales Order' at schedule line category level

And Billing relevance should be 'G' Invoice against Goods receipt quantity at Item category level.
Billing Quantity at Copy Control should be ' E'

In this case upon Goods receipt Customer invoice can be generated against GR quantity.

If business requirements are to generate auto Purchase order the below additional setting need to be done.

1. Auto PO check box needs to be enabled at  Material and Vendor Master Data level
2. Source List and Info record need to be maintained for the specific material and Vendor combination.

But how come system control creation of customer invoice before dispatching goods to the customer ??

This will be done by copying requirement ' 12' at copy control item category level.

If this check is taken off, then we can raise customer invoice even before customer delivery.

Tracking of serial numbers cannot be done through standard process and this requires enhancement  to be done at GR level upon material document posting.
Thank You.



Comments

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).

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.

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...