Message type SHPCON, idoc type DELVRY01

Hi SAP Gurus,
I am using message type SHPCON and idoc type DELVRY01 with processing code DELV to post goods issue for a delivery note.
I tried to simulate the inbound entry via WE19. I was not able to proceed with the posting because I encountered error 51 in idoc.
Field EXIDV empty
Field VHILM empty
These fields are in E1EDL37 and E1EDL44 respectively, and referring to HU information in which we don't have.
What I have filled up are the fields:
E1EDL20-VBELN = DO num
E1EDL20-VSTEL = Plant
E1EDL18-QUALF = "PGI"
E1ADRM1-PARTNER_Q = "WE"
E1ADRM1-PARTNER_IQ = recv plant
E1EDTH13-QUALF = "015"
E1EDTH13-NTANF = date today
E1EDL24-POSNR = 000010
E1EDL24-MATNR = material num
E1EDL24-WERKS = delv plant
E1EDL24-LGORT = sloc
E1EDL24-LFIMG = quantity
E1EDL24-VRKME = unit
E1EDL24-LGMNG = quantity
E1EDL24-MEINS = unit
May I know how to avoid this or if I missed some fields that resulted to this error ? Or am I using the wrong message type?

Hari,
I can definitely use WE19 to reprocess it. However my problem is the source of this information. If we implement this process, we would not know where to get this information since we don't use handling units. To add to this, the field VHILM that the system is asking is "packaging material" which we don't use and don;t have.
How to get rid of these fields? In VL02N, there is no handling units when I click on the pack icon. Only the material and the quantity.
Thanks.

Similar Messages

Posting goods issue using Message type SHPCON and idoc type DELVRY03

Hi SAP Gurus,
I am using message type SHPCON and idoc type DELVRY01 with processing code DELV to post goods issue for a delivery note.
I tried to simulate the inbound entry via WE19. The scenario should be posting goods issue based on the delivery order.
In some cases, quantity issued is less than the quantity in the DO. For this, I need to change the delv quantity in the DO via VL02N before I select Post goods issue button. This will change at the same time post the goods issue.
What I have filled up are the fields:
E1EDL20-VBELN = DO num
E1EDL20-VSTEL = Plant
E1EDL18-QUALF = "PGI"
E1EDTH13-QUALF = "006"
E1EDTH13-NTANF = date today
E1EDL24-POSNR = 000010
E1EDL24-MATNR = material num
E1EDL24-WERKS = delv plant
E1EDL24-LGORT = sloc
E1EDL24-LFIMG = updated quantity
But everytime I simulate using WE19, the entire quantity in the DO is not changed at all. The goods issue quantity posted is still the original DO quantity.
May I know how to do this? Thanks.

Put value in E1EDL24-LGMNG for qty to pgi.

Batches not getting updated by incoming idoc DELVRY03 (message type SHPCON)

Hi
    I am using incoming idoc DELVRY03 (message type SHPCON) to update delivery document.I am using field E1EDL24-CHARG to pass batch data.
      However batch number is not getting updated in delivery document. I have verified aspects like batch number is valid etc.
     While updating batch number thru incoming idoc, do I need to supply some other data?
Please help.
TIA
Koustav

Hi Biswas,
I think batches are determined automatically in the deliveries while creation and thats the reason it is not getting the batch number in the delivery, if there is no automatic batch dertermination then it will update the valid batch number
also please check the batch determination procedure and the batch master in MSC2N and availability of materials for that particular batch
regards,
Santsoh

Outbound delivery with Inbound IDOC DELVRY06 with Message type SHPCON

Hi Friends
I am trying to pack outbound delivery with Inbound IDOC DELVRY06 with Message type SHPCON.
But IDOC has error Specification of destination HU missing.
Could you please help us to resolve the issue to Pack the outbound delivery with the IDOC.
Thanks
SR

HI Ian Kehoe
Sorry for delay in reply
Thanks you very much
I solved that problem .
Could you please advice test data for IDOC DELVRY06 packing hierarchy (multi level packing) to pack SAP outbound delivery.
Thanks
Ravi

Message types and idoc types

hi,
     i need the list of message types and idoc types for edi.
      can any one of u pls send it.

Hi,
Check the OSS notes 104606.
The following list maps the logical messages and IDoc types to the corresponding ANSI X12 transaction sets.That is, the logical message can be copied to the transaction sets named.
204 Motor carrier shipment information
           The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
214 Transportation carrier shipment status message
           The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
304 Shipping instructions
           The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
810 Invoice or billing document (also 880)
           The logical message is INVOIC, the IDoc type INVOIC01.
812 Credit and debit advice
           The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
820 Payment order and credit advice
           For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
           For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
823 Lockbox
           The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
830 Delivery schedule (LAB)
           The logic message is DELINS (from the EDI standard ODETTE) or DELFOR the IDOC type DELFOR01.
832 Price catalog (also 879, 888, 889)
           The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
834 Benefit enrollment and maintenance
           The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
840 Request
           The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
843 Quotation
           The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04.Outbound processing is supported.
850 Purchase order or order (also 875)
           The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
852 Stock and sale data
           The logical message is PROACT, the IDoc type PROACT01.
855 Order confirmation (also 865)
           The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
856 Transport and shipping notification (ASN - Advanced Ship Notification)
           For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
           For the delivery in the SAP application, the logic message is DESADV, the IDoc types DESADV01 (to be discontinued), DELVRY01 and DELVRY02.
860 Ordering modification (also 876)
           The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
861 Credit advice (ERS - Evaluated Receipt Settlement)
           The logical message is GSVERF, the IDoc type GSVERF01.
862 Delivery schedule (FAB)
           The logic message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDOC type DELFOR01.
864 Text message
           The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
940 Shipping order and stock order
           The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
945 Shipping confirmation and stock confirmation
           The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
997 Functional acknowledgment
           This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
           "22" Shipping OK, acknowledgment has yet to come
           "16" Functional acknowledgment positive
           "17" Functional acknowledgment negative
           The status values "14" and "15" are available for the Interchange Acknowledgment accordingly. Source code corrections
Cheers
VJ

Idoc type, message type and process code for EDI 940 & 945

Hi,
We are implementing a scenario wherein we are required to send a Wharehouse Shipping Order to the warehouse (forwarding agent) using EDI 940. The output of the o/b is triggered from the Delivery (VA01) after creation of a Delivery in SAP. Once the warehouse ships the goods, it notifies us back by sending EDI 945 (Warehouse Shipping Advice). Using this inbound 945 we are required to update the existing delivery in SAP, i.e., it should do the Pick, Pack and PGI.
Can someone tell me which Idoc type, Message Type and Process code should be used for the above scenario.
Thanks in advance for the help.
Regards,
Gajendra

Hi Gajendra,
For EDI940, you can use message type SHPORD or WHSORD, IDOC type DELVRY01 and process code DELV.
For EDI945, you can use message type SHPCON or WHSCON, IDoc type DELVRY01 and process code DELV.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Message Types in DELVRYxx IDocs

Can anyone tell me why SHPORD/WHSORD/SHPCON/WHSCON message types apply for idoc DELVRY03 but not for DELVRY05? I thought each new version of the IDoc would still be used for the original message types.
Thanks,
Keith

Maybe because of some problems. For example : [Note 971803 - No IDoc object types for SHPCON and WHSCON|http://service.sap.com/sap/support/notes/971803].
But I found no proof of this change! Normally it can't be changed without a note (I mean, without informing).
For information, this note created the messages : [Note 311664 - Assignment of IDoc type DELVRY02 is incomplete|http://service.sap.com/sap/support/notes/311664].

SHPCON message type

I am trying to simulate inbound 945 using the EDI message type "SHPCON" using WE19. While it is successful in updating the pick quantities, the overall Warehouse status is still showing as "B" (as a result of which I am not able to do PGI). How can I bring the overall warehouse status to "C"? Am I missing something? Thanks in advance

You cannot pick and PGI with one IDoc because there is only one qualifier field. You will need 2 IDocs: one to pick and one for PGI.

Idoc and message type not getting replicated in the receiver system

Hi
i have created a Z Idoc and didtributed the mode from system A ....I can see the distribution model in system B
However i cannot see the custom zidoc / message type in sys B.. Do i need to create the zidoc again in sys B

Hi Tarang,
at least ou need the required partner agreements and you should have a processing function for inbound IDoc. To implement this, the full definition of IDoc including Segment definition should be present in receiving system.
Just look at standard IDocs and do as they do.
Regards,
Clemens

Idoc message type for open orders & Open JIT lines

Hi,
I need to send Open Purchase Order data and Open JIT lines data to supplier daily via Idocs.
Is there any standard messege type available for this data.
Regards

Hi Rohita,
Instead of changing the standard domain, You have to make the changes in the User Exit.
Say Qualifier 001,002,003 were already there in the domain.
001--Purchase Date
002--Delivery Date
003--Ordered Date
In the user exit u have to just add the segment and the qualifier without making any changes to the Standard Domain.
These Qualifiers are just like other variables and u can add whatever values to them that u want..
You can add Qualifier 004 for Trnasportation Date or Goods issue date and have to communicate the MiddleWare informing that date with this Qualifier will be Transportation Date and they will do the mapping to the corresponding field in other syste.
You can have as many message types as u want for the same IDoc type. There is no harm in having multiple message type. And u dont need to change the standard domain. It can be done without changing the domain.
If u analyse the FM closely u will realise that they have done coding for those values in the domain.
So instead of adding it to domain u just have to do the coding for this new qualifier.
Revert back if u need any help on it.
Thanks...
Message was edited by:
Utsah Garg

IDOC Message type for open sales orders

Hi
We are trying to send the list of open sales orders of a customer in an IDOC to the customer. For example, if the customer has got 15 sales order to be delivered to him , he needs the details of all these 15 orders in an single IDOC
Is there any message type available for this in SAP R/3 4.7 version
Regards
Anandh

Try VA05 schedule lines standar variant...include status fields and both ordered qty and confirmed qty. In SAP standard system order status, status A means open orders fully (Nothing shipped, everything opened). Status B means in process orders (Partially processed - shipped). Status C means complete orders (Nothing opened). As there is no delivered qty in VA05, you need to download to excel the file and calculate the difference between both qty fields for each A and B status. That is a way to get the missing qty to be delivered or open qty as you stated.
Hope it helps.
Jorge Fernandez

Idoc Message type for Scheduling agreement

Dear Experts,
How to configure to create Idoc for Scheduling agreement (not the releaseed schedule lines) ?
I am trying to use message type ORDERS05 but it is not working.
Will any body guide me preferably step by step process for this ?
Thanks in Advance,
Best Regards,
Raju

Hi Anji,
Thanks for the Reply. But i think ORDRSP is for Order Confirmations.
But I have to send Outbound Idoc for a Schedule Agreement.
Whether the same Idoc type & Messge type used for SO/PO(e.g ORDERS05, ORDERS/ORDCHG) can be used for Scheduling Agreement.
Please Advice.
Regards,
Anbalagan

Message type for Scheduling Agreement - Outbound IDoc

Hi All,
I have to create an Idoc for Scheduling Agreement through a Z program based on some conditions. I have bit confusion, whether i can use Idoc type for Orders(e.g ORDERS01..05) & Message type ORDERS / ORDCHG to generate Outbound Idoc.
Already there is process code for for ORDCHG mappig IDOC_OUTPUT_ORDCHG & ORDERS mappig IDOC_OUTPUT_ORDERS. Whether there will be any impact on this.
Appreciate your help.
Regards,
Anbalagan.

Hi Anji,
Thanks for the Reply. But i think ORDRSP is for Order Confirmations.
But I have to send Outbound Idoc for a Schedule Agreement.
Whether the same Idoc type & Messge type used for SO/PO(e.g ORDERS05, ORDERS/ORDCHG) can be used for Scheduling Agreement.
Please Advice.
Regards,
Anbalagan

Error while trying to post inbound idoc of message type COND_A

Hi,
I am getting error while trying to post inbound idoc of message type COND_A.
If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
and if providing value in above fields then dump is coming.
How to solve ?
Plz do reply
Thanks
Mohit

I do not see any reason why you would need to use COND_A04 if COND_A01 is working.
What if you could get COND_A04 to post and you would face the same result as in COND_A01?
If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
fixed a situation where the vendor number was not validated.

Creation of New Message Type for Extended IDoc

Dear Friends,
I want to create New Message Type for MATMAS and want to Active Change Pointers accordingly. Thru this Message Type how can I able to use Extended IDoc which I have created for Basic Idoc Type MATMAS05.
I am Sending Data from SAP to XI ; Any one can help me in this How can I create the Message Type with the IDoc Extn .
for Change Pointers.
Warm Regards,
Naveen Mutyapu.

Hi naveen mutyapu,
see these links
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
http://www.allinterview.com/rss/interview-questions/new/SAP-ALE-IDocs.xml
happy learning.
thanks
karthik

Message type SHPCON, idoc type DELVRY01

Similar Messages

Maybe you are looking for