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

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

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

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