on 11-16-2009 3:33 PM
Hi Guys,
I got requirement as below,
Manipulate the GR time defined in the unloading point when the ATP confirmation of sales order is done with GATP online.
I noticed that the online GATP check from R/3 to APO is not going via normal CIF way of communication or at least even i de-registered CIF queue monitoring, the data transfer can still go through properly.
There are two questions popped up:
1. Any body knows the background routine how the data are transferred between R/3 and APO when online GATP is done, and how to debug this process?
2. Which functional module or exit user is called when online GATP check is done from R/3 sales order?
If anyone knows something you are also welcome to share your expertise!
Thanks!
Tony
Hi Tony,
FM called in R/3 is AVAILABILITY_CHECK
In APO if you want to manipulate scheduling then use exit EXIT_/SAPAPO/SAPLVCRM_002
use this exit with caution, you need an experienced developer.
Thanks,
Pavan Verma
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Pavan,
Thanks for your answer, I'm still in the course of understanding the scheduling logic. What i'm trying to manipulate is the unloading point. As it defines the possible GR time at customer, we want to allow every full day regardless the time window defined in the unloading point.
BR,
Tony
Hi Michael,
Thanks for your input!
We're already using EXIT_/SAPAPO/SAPLVCRM_002 to control the GI calendar, however, i still couldn't find how the unloading point is taken into calculation.
As GI calendar and transport calendar is defined in APO with time stream. But unloading varies per customer and it's maintained in customer master in R/3. In the structure that is transferred from R/3 to APO, i only see in the SD_DOC and ATPFIELD there's a field with name of unloading point but wonder how the details are communicated, meaning the open time window information.
Do you have any idea?
Thanks and regards!
Tony
hi! Tony
These are the Exits in online GATP
EXIT_/SAPAPO/SAPLATPT_001 APO ATP: Set ATP Segment
EXIT_/SAPAPO/SAPLATPT_002 APO ATP: Select Substitutions
EXIT_/SAPAPO/SAPLATPT_003 APO ATP: Initialize ATP Controller
EXIT_/SAPAPO/SAPLATPT_004 APO ATP: Check for the Existence of a Location Alias
EXIT_/SAPAPO/SAPLATPT_005 APO-ATP: Handling of Data at End of Check
Regards
Vaibhav Sareen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
9 | |
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.