on 07-08-2008 2:28 PM
Dear Experts
Kindly help with the following requirement:
There are 2 shipment types ZRLY for Rail and ZROD for Road.
There are 2 delivery types ZLRY for Rail and ZLRD for Road.
Now an instance can occur when ZRLY which is moving by rail is added to a Road Shipment type ZROD - We cannot allow this.
To summarize can we define allowed delivery type per shipment type in standard or can this be developed?
Regards
Siddharth Sridhar
Hi
I think that you have had your question answered so if you are happy with this can you please award points if you want to but mainly can you please mark your question as answered so that it is easier to navigate around the open questions in the forum as the number of pages are growing and growing and it takes too long to go through everything especially if a satisfactory answer has already been given and people like me who want to help will give up and so some people may not get any help.
Thanks for this
Frenchy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sridhar,
Can we define allowed delivery type per shipment type in standard or can this be developed?
I think as per the standard you can't restrict the delivery types to the specific shipment type.
So you need to go for some user exits with the help of ABAPer
These are the User Exits available in shipment document processing
V56AFCCH Shipment processing: Check function code allowed
V56AGTAR User Exit for Filtering Shipping Unit Calculation
V56ARCHV Customer-spec. checks for archiving shipments
V56ATKTX Change the number of lines for text input in shipment
V56BMOD Transportation processing: Field modification
V56DISTZ Shipment Processing: Determine Distance
V56FCOPY Shipment processing: Copy delivery data
V56FSTAT Shipment processing: Activities when setting a status
V56I0001 IDoc TPSDLS: Modification of delivery header group
V56I0002 IDoc TPSDLS: Modification of delivery item group
V56I0003 IDoc TPSDLS: Modification of package data group
V56I0004 IDoc TPSDLS: Modification of entire IDoc
V56I0005 IDoc TPSDLS: Modif. of delivery items relevant to shipm
V56I0006 IDOC TPSDLS: User-defined determ. for location substitu
V56I0010 IDoc TPSSHT01: Input of planned shipments
V56I0020 IDoc control record modification in interface SD-TPS
V56I0030 Freight Costs RFC from APO
V56IVIEW User exit for the structure of the planning overview
V56K0001 Outbound Transportation Output (EDI)
V56KBAPI Enhancement for Calling Shipment BAPIs
V56L0001 Status of Shipments for a Delivery
V56L0007 Deactivate multiple transmission lock for deliv. to TPS
V56LDELI Read Delivery Data for Shipment Processing
V56LOCID Shipment Processing: Determine Location Identification
V56MVT04 Extensions for Collective Processing of Shipments
V56SLDET Shipment processing: Leg determination
V56TDLIF Filter Delivery Items for Shipment
V56UCHCH Shipment processing: Check whether changes were made
V56UCHCO Check shipments are complete
V56UDLUP Obsolete as of 4.6C: Delivery Update on Delivery Routin
V56UNUMB Shipment number allocation
V56USTAT User-individual definition of transportation planning s
V56USVDO Update new objects for transport
V56USVDP Preparation for updating new objects for transport?
I hope it will help you,
Regards,
Murali.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
97 | |
10 | |
9 | |
6 | |
3 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.