on 02-23-2011 10:20 PM
I have question on APO GTAP
If I understood the concept correct, you define the ATP check options in Integration model and replicate to APO
carry out GATP (rule based ) in APO.
you create sales orders in SAP ECC and CIF them to APO
What happens to the sales orders? are you assigning the delivery or confirmed quantity in APO and sending it to ECC?
Hi, Rama Bhupal
Assuming that ECC and APO side done the all configuration. MTO scenario- when you create a sales order in ECC side, system will check the ATP in APO through CIF. based on your rule system will carryout the ATP (e.g ; Alternate location /product also)
if stock Qty match the demand - system confirm the qty either from same location/product or alternate location /product and update the sales order schedule line delivery date
If stock qty not match the demand- system trigger CTP (based on configuration) and create planned order and update the sales order schedule line delivery date
bye
Dhaiva
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dhiva
say I created sales order for 100 quantity of charis required on 1st of march
as of now 40 is confirmed.( by checking ATP rules set up in ECC/APO)
question is
will this sales order CIFed to APO? and update the remaining 60 quantity immediately in ECC
or the sales order CIFed to APO, Do availabilty check product/locatoin, allocated the confirmed date & quantity in sales order in APO itslef? then release it ECC?
another question is
say I created sales order for 100 quantity of charis required on 1st of march
if on 1st march only 60 quantity is available for delivery & ATP
The sales order should appear in Back orders.
in ECC you need to check and process back orders manaually.
How the scenario works when we implement APO GTAP? and how do check back orders processing is complete
Rama,
There are at least two Integration models that will be used here. One for Sales order (replicates the sales order in SCM) and another one for ATP (passes confirmations back and forth). Generally, the transactional data required by ATP is mirrored in both systems at all times using integration models in the Core Interface.
So, for existing SOs, (including existing partially confirmed SOs) all relevant data (stock, purchase orders, etc) is replicated in SCM, prior to performing the ATP. Now you perform an ATP (in R/3). The system immediately and transparently goes to SCM, performs the ATP check that you have configured, based on data found in SCM. It sends the results back to R/3, and when the user accepts the proposal, the results are recorded in both systems. The same process happens during sales order creation as well.
The method of processing Back orders in SCM is - BackOrder Processing. This is a submodule of GATP. It can be done interactively, or in batch, same as R/3.
Best Regards,
DB49
Rama,
Application logs can also be viewed using SLG1 in APO, and deleted with SLG2. There are other APO log transactions that basically call up the same log database, but SLG1 can be used to view any log object, and is handier.
Basis logs (database and filesystem type logs) are the same as R/3.
For more monitoring type info, check out the Service Marketplace site
http://service.sap.com/~sapidb/011000358700005273182001E
Its not all SCM but some good articles.
Best Regards,
DB49
User | Count |
---|---|
8 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.