EDI for 856 inbound

Hi Experts,
Please help me how can I add a new field in EDI for 856?  I'm not a EDI/IDOC developer.  I have a need to add a new field for incoming 856 EDI.  I found a field in IDOC to map my requirement, but my EDI/IDOC developer is asking me where do we map this in EDI?  Could some-one help me identifying an existing field or adding a new field to EDI?  What's the recommendation?  Please help me on this.
Appreciate your help.  
Thank you.
with regards,
Muthu Ganapathy.

Hello Muthu
First of all I have to point out that it took me about half an hour to find out the essential data related LGPBE ( Storage Bin ). It would have been much easier if you had provided these details in the first place.
Nevertheless, the definition of data element LGPBE was giving me the crucial input:
Definition: storage bin
     Warehouse Management (LE-WM)
     The smallest addressable unit of space in a warehouse, referred to as a
     "slot."
     Because the address of a storage bin is derived from a coordinate
     system, the bin is referred to as a coordinate, for example, 02-04-03
     refers to row 02, stack 04, level 03.
     Warehouse Management (LE-WM)
     Smallest addressable unit of space in a warehouse (often referred to as
     a "slot").
     Since the address of a storage bin is frequently derived from a
     coordinate system, the bin is referred to as a coordinate; for example,
     02-04-03 refers to row 02, stack 04, level 03.
I cannot tell you which field in the ANSI 856 message you need to fill.
Presumably I know which segment one should fill in case of UN/EDIFACT D.96A DESADV message.
Based on this it should be quite easy for you to find the corresponding segment in message 856.
Reference: [Edifactory: D.96A DESADV|http://www.edifactory.de/msginfo.php?s=D96A&m=DESADV]
  Segment group 15: LIN-PIA-IMD-MEA-QTY-ALI-GIN-GIR-DLM-DTM-FTX-MOA-SG16-SG17-SG18-SG19-SG20-SG23
Condition: C,9999
A group of segments providing details of the individualdespatched items.
Segment group 18 contains the segment LOC which most likely is the right place for the storage bin information.
  Segment group 18: LOC-NAD-DTM-QTY
Condition: C,100
A group of segments giving location information and whererelevant, additional addresses, date and time, andquantities.
    LOC, Place/location identification
    Condition: M,1
    A segment identifying a specific location to whichproducts will be delivered.
Segment LOC has the following structure:
Segment LOC
PLACE/LOCATION IDENTIFICATION
To identify a country/place/location/related location one/related location two.
Structure
3227      PLACE/LOCATION QUALIFIER      M      an1..3
C517      LOCATION IDENTIFICATION      C      
  |      3225      Place/location identification      C      an1..25
  |      1131      Code list qualifier      C      an1..3
  |      3055      Code list responsible agency, coded      C      an1..3
  |      3224      Place/location      C      an1..70
C519      RELATED LOCATION ONE IDENTIFICATION      C      
  |      3223      Related place/location one identification      C      an1..25
  |      1131      Code list qualifier      C      an1..3
  |      3055      Code list responsible agency, coded      C      an1..3
  |      3222      Related place/location one      C      an1..70
C553      RELATED LOCATION TWO IDENTIFICATION      C      
  |      3233      Related place/location two identification      C      an1..25
  |      1131      Code list qualifier      C      an1..3
  |      3055      Code list responsible agency, coded      C      an1..3
  |      3232      Related place/location two      C      an1..70
5479      RELATION, CODED      C      an1..3
Finally, have a look at qualifier '129' for data element C517-1131:
129       Customs warehouse
     Identification and/or location of the Customs warehouse in which goods will be or have been deposited (CCC).
Regards
  Uwe

Similar Messages

  • EDI for creation of Sales Order and sending copy of Invoice

    Hello Experts,
    I am working on EDI. We have a scenario, where the purchase order created in the 3rd party system has to be converted into a sales order in our SAP system.
    Then, the regular flow would follow uptil delivery and creation of invoice in SAP.
    We have to send a copy of this Invoice back to the 3rd party system.
    So, in effect, we would have EDI at two points, while capturing the PO from the 3rd party and another when sending a copy of the Invoice back to the 3rd party.
    Please advise on how to go about implementing EDI in the above mentioned scenarios.
    Regards,
    Divyata

    Use EDI 850 Process code ORDE FM IDOC_INPUT_ORDERS for PO (Inbound)
    use EDI 810 Process code SD09  FM IDOC_OUTPUT_INVOIC for Invoic (Outbound)
    Edited by: srini korada on Jun 9, 2011 4:51 PM

  • IDoc Receiver, Error in we02 - EDI: Partner profile inbound not available

    Hi All,
    I have a problem when creating a receiver IDoc from XI to R/3.
    I have successfully tested the IDoc when populating the receiver information from the payload. However I want this information to be populated automatically based on the logical systems.
    When I do this I get the following error in the IDoc in R/3:
    EDI: Partner profile inbound not available
    In the control record the sender information is all correct but in the recipient information the partner Number with type LS is populated, but port is not populated.
    I have done the following steps.
    •     the sender is a Business Service so I have created a logical system directly adapter-specific identifiers in the sender service in the integration directory.
    •     In the receiver business system I have imported the logical system into the adapter-specific identifiers in the ID from that specified in the SLD.
    •     In the receiving R/3 system using SALE/BD54 I have created a logical system for the source system.
    •     In the receiving R/3 system using we20 I have created a partner profile of type LS with the same name as the source logical system.
    •     IN PI/XI system in transaction IDX1 I’ve created a port (SAP<SID> where <SID> is the system ID of the receiving R/3 system) and the client of the R/3 system, and the RFC destination of that system (<SID>CLNT<clnt>, as specified in SM59).
    •     In the IDOC Adapter (receiver) I have entered the RFC destination and port matching those created above. All checkboxes are UN-checked eg. take sender from payload, take receiver from payload, Apply control record values from payload, etc. are all NOT checked.
    I think that I’ve done everything correctly, but I get the error in we02 in R/3: “EDI: Partner profile inbound not available.”
    Any help will be greatly appreciated (and rewarded, obviously).
    Thanks,
    Matt.

    HI Matt,
    Can you please copy paste the exact error message....In your error message it will show you Exact partner Number / Logical System name and other parameters...just compared if you have all parameters set in your partner profile comparing to error message...
    If you can giev screen shot of both..then probably would be easy to point out error.
    Hope this will help.
    Nilesh

  • Invoice EDI error : EDI: Partner profile inbound not available

    Hi  EDI experts ,
    We are connecting our SAP ECC 6 ( Ehp 4) system to 3rd party system Mincom via SAP PI, to send PO Creation message (Outbound) and receive Vendor Invoice message( inbound).  We already done all the settings..Output determination procedure, Partner Profile ( WE20) , Port creation , Condition Records, EDI settings in SPRO for invoice..etc as below:
    Logical system ( BD54)
    ECC system - EDACLNT112,
    PI systems u2013 IDACLNT210
    Third party u2013 LSMINCOM
    Port ( WE21)
    IDACLNT510 : For PI with RFC destination IDACLNT510
    Partner ( WE20)
    LSMINCOM :  (Partn.Type LS)
    Outbound parmtrs.- Partner Role- LS, Message : ORDERS , Port - IDACLNT510
    Inbound parmtrs.- Partner Role- LS, Message : INVOIC , Message Variant- MM, Process code u2013 INVL, Trigger immediately (Process code INVL have  Identification - IDOC_INPUT_INVOIC_MRM, Option ALE u2013 Processing with ALE services , Processing type- processing by functional module)
    Here PO Creation is working fine . IDoC of PO outbound message have below details :
    Recipient information:
    Port :     IDACLNT510 (Logical system & Port created in WE21 )
    Partner Number :  LSMINCOM   ( Logical system and Partner created in WE20)
    Partn.Type :  LS        
    Function :  LS     
    Sender information:
    Port :  SAPEDA ( donu2019t know how it created..but in WE21..it is not there)
    Partner number:   EDACLNT112 ( Logical system and Partner created in WE20)
    Partn.Type :  LS        
    Partner Role :Blank
    Just started testing, our PI team is sending the IDoC, with wrong information on partner & other data, so inbound IDoC failing with error u201CEDI: Partner profile not availableu201D. Oaky. I reprocessed these failed IDoCs by changing Partner data just opposite (i.e. Sender info as Recipient info & vice versa) to successful PO Creation O/B message in WE19 in EDIDC and when I click on u201CStandard Inboundu201D, then another window open giving error message u201CPartner profile not maintainedu201D and creates new IDoC with status 56
    EDI: Partner profile inbound not availableMessage no. E0337
    Diagnosis
    An inbound partner profile could not be found with the following key:
    /LSMINCOM/LS//INVOIC///X/
    This involves the key fields of table EDP21:
    -SNDPRN  partner number of sender
    -SNDPRT  partner type of sender
    -SNDPFC  partner function of sender
    -MESTYP  logical message type
    -MESCOD  logical message code
    -MESFCT  logical message function
    -TEST    test flag
    Procedure
    Please check the inbound partner profiles.
    Execute function
    I am not getting exactly what inbound partner profile could not be found or what is the problem here . Can anyone suggest me what should be the problem and solution on it ?
    Thanks
    NAP

    Narendra,
    Please advice what was the solution.

  • EDI: Partner profile inbound not available Message no. E0337

    Hi Friends,
    I am facing very wiered issue for incoming vendor frieght invoice. When the IDOC is sent to SAP from the edi subsystem, it gets posted with status 56 and error message
    EDI: Partner profile inbound not available
    Message no. E0337
    Diagnosis
    An inbound partner profile could not be found with the following key:
    /0040000010/LI/VN/INVOIC/MM///
    This involves the key fields of table EDP21:
    -SNDPRN  partner number of sender
    -SNDPRT  partner type of sender
    -SNDPFC  partner function of sender
    -MESTYP  logical message type
    -MESCOD  logical message code
    -MESFCT  logical message function
    -TEST    test flag
    I have created the partner profile in WE20 for Partner type LI, partner role VN and process code INVL, message type INVOIC, message code MM. I have also checked the entry in TABLE EDP21 and the entry exists.
    When I open the IDOC in WE19, and click on standard inbound TAB it says partner profile not maintianed, however when i click on the control record it opens a dialog box, where we have all the entries for partner profile and when I just click on any field in the dialog box and click continue and when again click on standard inbound it say partner profile maintained.
    None of the data is changed in the IDOC control record, I just click on any field and it finds the partner profile.
    Please let me know your thoughts, what could be possible reason and a solution.
    Thanks
    Deepak

    Hi Deepak,
    I am facing the same problem with a different message type.
    But same effect. I can copy the IDoc with WE19 and it will process nicely, completely unchanged.
    Have you found the reason for this?
    Thanks,
    Florian

  • Error 56 "EDI: Partner profile inbound not available"

    I am tring to post IDOC using we19.
    Bu t, I am getting the error 56 "EDI: Partner profile inbound not available"
    Could any one please suggest me ..how to solve the problem.

    Hi Sam,
    When you process the inbound IDoc using standard inbound button, the system will perform validation for a given IDoc control record against the partner profile and file port setup. In your case, there is no inbound partner profile setup (WE2) for the corresponding message type. Therefore, you got an error message 'Partner profile not maintained'.
    When you process the inbound IDoc using inbound function module button, the system will <b>NOT</b> perform validation against the partner profile and file port setup. The system will call directly the inbound FM to process the inbound IDoc. You may get an error based on validation of IDoc data record within the inbound FM.
    In production environment (real case), the system will always validate againts the partner profile and file port setup for incoming IDoc.
    Therefore, it is important to have ALE and IDoc corretly setup for inbound and outbound message types.
    Again, hope this will help.
    Regards,
    Ferry Lianto

  • Edi partner profile inbound parameters urgent plz

    hi
    iam trying to make settings for inbound parameters of edi for bank, iam wondering what is partner number if partner type is "b"(bank). my partner number will be bank key or house bank or what , bcoz it is not accepting bank key or house bank id

    Hi,
    In Transaction code FI12 - Change House Bank - Details, there is an push button to create EDI Partner Profiles. Click on that and enter the EDI Partner number. This is not House Bank number / Bank Key. After entering the EDI Partner number, you can click on Partner Profiles and complete the setting up of Partner Profile.
    Thanks
    Murali.

  • How to Identify EDI errors in inbound IDocu0092s?

    hi,
    I just want to know how to identify EDI errors in inbound IDoc’s?

    Hi
    Ref this links
    http://www.hibcc.org/EBUS/editemplates.htm
    /people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
    /people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
    /people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
    /people/sravya.talanki2/blog/2005/12/02/manipulating-idoc-control-records-from-payload
    /people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
    /people/ravikumar.allampallam/blog/2005/02/28/creating-sales-order-through-idoc
    With Seeburger we can conver to edi format to XML
    seeburger doc
    http://www.stylusstudio.com/edi/XML_to_X12.html
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
    Details on XI EDI adapter from seeburger
    Doc for Conversions-
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    SAP Adapters
    EDI with XI
    http://www.seeburger.com
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
    http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
    http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
    Thanx
    Bommireddy.Sridhar

  • EDI 810 ,856

    Hi all,
    Please doea any body can provide the step by step process for EDI 810 & 856 . i donno how to create edi 810 and 856.
    Thanks in advance.

    Hello Shweta
    EDI 810 = Invoice, e.g. [EDI 810 Invoice Defined|http://www.edipipeline.com/810.asp]
    EDI 856 = Advanced Ship Notice, e.g. [EDI Engineu2122 \ Translation \ ASC X12 \ 856 (Advance Ship Notice/Manifest)|http://www.123edi.com/edi-856.asp]
    The basic steps of EDI are:
    1. Send SAP invoice / outbound delivery as EDI output (IDoc message types: INVOIC and SHPORD (DELVRY03)).
    2. Receive IDocs at EDI conversion platform (e.g. SAP-XI).
    3. Convert IDoc-XML to EDI-XML.
    4. Convert EDI-XML into flat EDI message.
    5. Send EDI message to receiver mailbox (e.g. via VAN or AS2 or OFTP)
    Regards
      Uwe

  • TD503 Element in 856 Inbound

    Hi Gurus
    In 856 inbound, where the element TD503 (SCAC) code from segment TD5
    should pop up in SAP.

    Hi,
    If you are working with 856 Pick Pack Advance Ship Notice to SHPMNT02 IDoc, then it should be mapped to segment E1ADRM1 field PARTNER_Q.
    For more information on data mapping, please check this document.
    http://www.erpgenie.com/sapgenie/docs/856.xls
    Regards,
    Ferry Lianto

  • How to block the status mail for an inbound Idoc to a specific user

    Hi,
    I have to stop sending the error status mail to a specific user depenidng on Partner Type. This will trigger when an inbound Idoc contains status error(message type INVOIC &ORDRSP).This user needs other mails which are getting triggered with the same Idoc for the same partner. Basically, the requirement is to block only the status mail for that user. The statndard task for this is TS70008125 and it uses the agent determination rule 30000001 (Idoc Administrator).in WE46, this task is assigned to process code EDIR. I have copied the task to a custom task and changed the agent determination rule. I would like to know how will I configure this task so that this custom task will trigger for the status error, without altering other workflows for the same message type & the partner type. Or is there any other way to block the mail?
    Thanks,
    Santosh

    Hi,
    I have done the required coding to exclude the specific agent from the rule,copied the task and its ready. My question is how do I map this custom task to a particular partner type, for the message type INVOIC in WE20? (The message type used for the inbound Idoc is INVOIC). I checked the Partner profile in WE20. Most of the process code is using function module as the processing type.
    Thanks,
    Santosh

  • Error while posting MIGO for HU-Inbound Delivery

    Hi All
    When am trying to post the MIGO for HU Inbound Delivery Creation, am getting an error saying "Required parameters missing when calling up module MARV_SINGLE_READ". 
    Following areas I have verifed:
    The posting periods in MMRV shows current period.
    The Number range for HU ID and Delivery type HID is maintained.
    Now am looking for your expert opinion to resolve this issue.
    Regards
    K. Viswanathan

    Are you getting the same error in  transaction MB1C to create the delivery.Try in MB1C

  • EDI FOR ORDER TO CASH CYCLE

    Hi,
    i am new in edi.
    what are step to implement edi for order to cash cycle.
    what are the idoc we are going to use in this scenario.
    and what are the edi we used for this scenario.
    If anyone has any material for this scenario then please give me link..
    it will be very helpful.
    Thanks,
    Jigar

    Hi Jigar,
    Please check this online documents for ALE and IDoc.
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Also check this links for additional information.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    Hope this will help to start with.
    Regards,
    Ferry Lianto

  • Error : Pre Settings for IDoc inbound processing are missing error

    Hi Experts,
    There is a CRM job which executes LSMW and I am facing a strange problem during the IDOC posting the error "Pre Settings for IDoc inbound processing are missing error". Can anyone please tell me how to correct this error?
    Thanks in advance.
    Madhurima.

    I'd start with the following document, with one modification. At step 12 after typing GEARAspiWDM press the Enter/Return key once prior to clicking OK. (Pressing Return adds a carriage return in the field and is important.)
    [iTunes for Windows: "Registry settings" warning when opening iTunes|http://support.apple.com/kb/TS3299]

  • BDC for MIGO-inbound delivery

    Dear Gurus,
    I want to create a BDC for GR-INBOUND DELIVERY.Is there any process that we have to upload two text files one at header level & one at item level.Pls suggest if there is any other method. 
    Regards,
    Prasad.

    1)Create a recording of inbound delivery creation if u want to create in mass.
    2) Make a note of all the filds recorded and make a excel sheet then convert it in notepad.
    3) Upload it by LSMW.

Maybe you are looking for