Help on Message type ANSI X12 *867*

Hi All,
Here my client has requested that he want to send Message type 867 as outbound to some of his customers. After making some reserch i came to know that this 867 uses SLSRPT message type in SAP but my problem is that we dont have this message type in our system (SAP 4.7). so do we need to create idoc type slsrpt starting from scrach (creating new segments, idoc type, message type ) or is there any alternate to this.
Please advice.
Thanks......

Hello
At the link [http://service.sap.com/ale] you find the following path:
Application Link Enabling
EDI Applications
(Document)      "EDIFACT Messages and their IDoc Counterparts"
When you open the document you will find the following entry:
EDIFACT Message     Directory     Area     Description     SAP message     IDoc Type     First availability     Directions
SLSRPT          Trade     Sales Data Report     PROACT     PROACT01     4.5     Out/In
Thus, you may give a try to IDoc message type PROACT.
Regards
  Uwe

Similar Messages

  • ANSI X12 867 Outbound or Inbound... ?

    Hi All.
    My client want to send idoc type 867. i dont understand is this a inbound idoc or out bound. I was told that 867 is SLSRPT message type in SAP but not able to locate its process code. can some one give me its details like the process code, message type and idoc type for sending ANSI X12 867. what are the setting we need to do in order to send 867's as an outbound...?
    Thanks
    Chindam P.

    Hi ravi,
    Thanks for your reply. I went into SAP to see what is this PROACT and i could see it as inbound and the process code is IDOC_INPUT_PROACT but i need a outbound where i want to trigger a outbound idoc which sends 867's.
    Thanks....

  • EDI ANSI X12 and relavent IDOC types and messages...

    Hi ,
        Is there any place where we can get the relevant Idoc types and messages for EDI Transacitons below:
    210 -Motor Carrier Freight Details and Invoice
    240 -Motor Carrier Package Status
    753 -Request for Routing Instructions
    754 -Routing Instructions
    816-ORGANIZATIONAL RELATIONSHIPS
    828-Debit Authorization
    846- Inventory Inquiry/Advice
    870-Order Status Report
    Could you please help me?
    Thanks and regards,
    gowri

    EDI ANSI X12 and relavent IDOC types and messages...
    Posted: May 25, 2006 8:44 PM        Reply      E-mail this post 
    Hi Ravi,
         Thanks a lot for the reply. I have already checked this. In the ittoolbox.com is having some info about 214 but not about 210 and 240. I have already gone through the sapgenie.com but could able to get the relevant info on below transactions.I am basically looking for relevant idoc types and messages  in SAP for the below ansix12 transactions .
    Is there any place where we can get the relevant Idoc types and messages for EDI Transacitons below:
    210 -Motor Carrier Freight Details and Invoice
    240 -Motor Carrier Package Status
    753 -Request for Routing Instructions
    754 -Routing Instructions
    816-ORGANIZATIONAL RELATIONSHIPS
    828-Debit Authorization
    846- Inventory Inquiry/Advice
    870-Order Status Report

  • IDOC Types and their equivalent messages in EDIFACT and ANSI X12

    Hi all, since I only have a list of messages in EDIFACT and ANSI X12 for release 4.6 B, I need to update the list from 6.0 version, but I don't have online support system to get it (OSS), it's note 104606 in OSS.
    Can somebody give me a link to the full new updated list? Will surely give points with your helpful answers
    Regards,

    Hi,
    Please check these perhaps they may help.
    Mapping ANSI X12 to SAP Message Type and IDoc Type:
    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), EDI - Inbound INVOIC posting configuration
    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 logical message is DELINS (from the EDI standard ODETTE) or DELFOR, the IDoc type is 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 Ordering or order response (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 delivery in the SAP application, the logical message is DESADV, the IDoc types are DESADV01 (expires) or DELVRY01 and DELVRY02.
    860 Ordering or order 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 logical message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDoc type is 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.
    Regards,
    Ferry Lianto

  • For ANSI X12 standard message will I get .sda and .xsd

    Hi Experts,
    For standard message will I get any .xsd and .sda files for EDIFACT and ANSI X12 etc... from SAP. OR
    If I get STANDARD MESSAGE only .xsd then it is required to create .sda and message type by using BIC MAPPING DESIGNER.
    Please kindly help me in this regards
    thanks and regards
    walter

    Stephen,
    If you want to use the standared ones then when you buy the Seeburger adapters they will provide you. You may need to create your own sda files when you change their standard ones.
    Regards,
    ---Satish

  • Need help for new message type for PO archiving

    Hello All
      I have configured new message type ZARR for PO archiving process. After configuring all the steps this condition is not getting picked to by itself. And after maintaing it manually it is giving red flag without any error message. Here I am listing all the step that I have followed for config. Please help me am I missing something or any parameter is wrong.
    Steps for new Message Type for PO Archiving
    1.     Defined new Table 513 Purch.Org./Plant.
    2.     Defined new access sequence Z513 Access Sequence for Archiving.
    Following are parameters to the Access Sequence
    Access Sequence Number = 21
    Table = 513
    Description = Purch.Org./Plant
    Requirement = 101
    Exclusive = Yes (box checked)
    3.     Maintain Output Type ZARR for PO
    General Data
    Access Sequence = Z513
    Access to condition (Checked)
    Multiple Issuing (Checked)
    Program = FM06AEND
    FORM Routine = CHANGE_FLAG
    Default Values
    Dispatch Time = Send Immediately (when saving application)
    Transmission Medium = Print Out
    Storage System
    Storage Mode = Archive Only
    Document Type = ARCHIVE
    Mail Title and texts
    Language = EN
    Title = Archiving for Legal Requirement
    Processing Routines
    Transmission Medium = 1 (Print Out)
    Program = SAPFM06P
    Form Routine = ENTRY_NEU
    Form = ZJ_9H_MEDRUCK
    Partner Roles
    Medium = Print Out
    Funct = VN
    Name = Vendor
    4.     Fine-Tuned Control: Purchase Order
    Oprat. = 1
    CType = ZARR
    Name = Testing for Archivin
    Short Text = New
    Update Print Related Data = Yes (checked)
    Oprat. = 2
    CType = ZARR
    Name = Testing for Archivin
    Short Text = Change
    Update Print Related Data = Yes (checked)
    5.     Maintain Message Determination Schema: Purchase Order
    Procedure RMBEF1
    Step = 100
    Cntr = 1
    CTyp = ZARR
    Description = Testing for Archivin
    Requirement = 101
    6.     Assign Schema to Purchase Order
    Procedure RMBEF1
    7.     Define Partner Roles for Purchase Order
    Out. = ZARR
    Med = 1 (Printout)
    Funct = VN
    Name = Testing for Archivin
    Name = Vendor
    8.     Test Condition Maintained in MN04 (Master Data)
    Purch. Org. = 0001
    Plant = 24
    Partner Funct = VN
    Medium = 1 (Printout)
    Date/Time = 4 Send immediately (when saving application)
    Output Device = HUL1
    Storage Mode = Archiving only
    Thanks
    Ankit

    the problem is the Exclusive = Yes  indicator in the access sequence.
    Your other message has this exclusive indicator as well.
    so if the first  message is found, then no other message wil be determined
    to allow several messages in one PO, you must not set this exlusive indicator

  • What is the message type and basic type used for catsdb in idoc help me

    what is the message type and basic type used for catsdb in idoc help me
    ANY IDOC FOR CATSDB PLEASE TELL,
    Regards,
    Jagrut BharatKumar Shukla
    points will be awarded

    Hi,
    Check these message types.
    ATT_ABS_WITH_COST and WORKSCHED_WITH_COST.

  • In which table cound i find the info on EDI standard Message type??

    Example
    EDI standard Message type Business process
    EDIFACT ORDERS Purchase order
                   INVOIC Invoice
    ANSI X12  850 Purchase order
                    810 Invoice
    Like those 850..810..etc info, i dont know from which table could i find the related info?
    Thanks.

    Hi Hoo,
    Electronic Data Interchange (or EDI) refers to the use of computers in formatting and exchanging business information using internationally recognized standards and formats. Standards organizations throughout the world have defined hundreds of document types to create a universal language for companies to conduct business while using dissimilar systems and processes. Common business documents, such as the invoice, purchase order, production planning schedule, ship manifest, and customs declaration, have been standardized and are sent and received electronically over private secure networks (Value-Added Networks - VANs) and the Internet.
    So EDI is not an SAP product, It is a method to exchange the data over internet.
    You dont get any information in any table in SAP. SAP supports EDI to exchange the data over internet. There are no. of third party EDI tools to connect to SAP.
    following is link to know more about EDI message types.
    http://www.edifactory.de/messages.php?s=D96A

  • ANSI X12 meta data availability in conversion agent??

    Hello,
    Is there a provision for availability of ANSI X12 meta data in SAP conversion agent. We are trying to process EDI orders using the X12 INDUSTRY standard. Please advise.
    -Kris

    hi,
    SAP Conversion Agent together with SAP Net Weaver, enables  to automate complex integration activities for a multitude of data and document formats. These include unstructured and partially structured documents such as Office files, data streams, printing applications, and other application-specific formats.
    Easily integrate unstructured and semi-structured data into SAP Net  Weaver Process Integration using the Conversion Agent.
    Conversion Agent dynamically converts unstructured messages from   Microsoft Word,Excel,PDF plain text. 
    Semi-structured formats such as HL7,SWIFT,HIPA, ANSI X12 and COBOL to   PI understandable SOAP XML.
              So that it helps to easily integrate the information need into the back-end systems. Conversion can also be used as the reverse process to convert from XML to unstructured or semi-structured formats
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sap%2bconversion%2bagent%2b-%2bthe%2blong%2bjourney
    Conversion Agent - Handling EDI termination characters
    Conversion Agent a Free Lunch?
    Integrate SAP Conversion Agent by Itemfield with SAP XI
    regards
    sr

  • 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

  • Message type ,IDOC TYPE , PROCESS CODE for Edi 990

    Hi ,
    Please provide the Message type ,IDOC TYPE , PROCESS CODE for Edi 990 (Response to a Load Tender).
    Thanks in Advance.
    Ajay Kolla

    Hi
    Pls check the below links
    1. http://www.erpgenie.com/sap/sapedi/ansi.htm
    2. http://www.erpgenie.com/sap-technical/ale-edi-b2b/master-data-message-types-idoc-types
    Hope this may helps you.
    Regards
    Sirigiri

  • Regarding message type SEQJIT

    Hi all
       please tell me the equilant ANSI x12 txn  number for message type SEQJIT .
    Thanks

    Hi Pavan,
    There is no hard and fast rule that you use standard or custom message types...
    SAP has provided messages for almost all scenarios. If you don't have enough fields in standard messgae type, you can enhance it to accumulate your requirement.
    But if the organization has completetly custom defined system (involving many Z-tables) , we create custom message types...
    As far as my knowledge, we should try to go ahead with standard message types by suppressing unnecessary segments and enhancing existing segments just to avoid Z-objects.
    Regards,
    Audy

  • Steps to Process standard EDI ANSI X12 997 file from AS2 Server

    Hi All,
    I have a scenario where we are receiving PO files from an EDI third party via AS2 adapter.
    In return, we are sending PO Acknowledgement and Invoice files to the third party via AS2 adapter.
    The fomat of the incoming and outgoing files are ANSI X12 (850 for PO, 855 for PO Ack and 810 for Invoices).
    Currently client has informed that they are going to send an EDI ANSI X12 997 (Functional Ack) file for each PO Ack or Invoice they receive.
    Kindly let me know steps to configure in SAP PI 7.1 to accept the inbound 997 files successfully and place them as it is in PI application server.
    Regards,
    Subhajit.

    Hi , I too have the same requirement.
    i am using
    Jdev 11.1.1.6
    Oracle Editor : 7.0.5.4016
    Document Protocol : EDI_X12
    Document type : 810 (Invoice )
    Version: 4010
    Weblogic server :11.1.1.6.0
    I followed all the steps to create EDI X12 810 ecs file, converted this to .xsd and then to .dat in Oracle Document Editor as explained in the B2B user guide.
    I also configured the trading partner , created agreements and deployed in B2B console. There is no mistake . as i can able to see the def file while configuring Oracle B2B in my Jdev.
    I deployed the same process . But no instance is creating for my process. I also configured listing channel to Generic File 1.0. please help me out in this . Thank you.

  • Process shipment status (ANSI x12 214)

    Hi,
    We would like  to integrate with our carrriers and as a start we would like to receive the shipment status back into SAP. The EDI message that our carrier will be sending is the ANSI x12 214. Can someone explain the actions that need to be taken to process these messages into our SAP system? We are using ECC6.0.
    Regards,
    Ed

    HI
    I am unsure about the Idoc type or message type which reciev the shipment status from the carrier. once we have the Message type we can do necessary set of Idoc configuration and run the shipment file which we will receive from EDI sub system and load in to SAP tables or transactions.
    Regards,
    Ram.

  • About the elusive message type 210.

    Hi all,
    Does anybody have ANY Document on message type 210 FrghtDet This is an Ansi X12 message but I can not find any details on the Internet at all.. Searching FrghtDet in Google gives no results.. Is there no website for FMDs and ANSI x12 at all??
    Also I wanted some good resource in EDIFACT standards but right now I really want to find the full details of 210.
    Thanks everybody,
    Charles.

    Hi Charles,
    EDI 210 Messages are used to transmit Freight Charges (Officially "Motor Carrier Freight Details and Invoice"). 
    We created an INVOIC IDOC to post these charges by mapping the necessary fields, and equating the SCAC codes to freight conditions that had been configured on the POs.
    In our case, we could get 1 Freight Bill (EDI 210) covering several POs, so we created separate INVOIC IDOCs for each PO referenced on the Freight Invoice.  actually, we allocate charges to each line item on each PO, but it is on INVOIC IDOC.
    If you Google "EDI 210" you can find many examples of implementation guides.  I suggest you start studying one of a partner that you are currently doing business with.
    CN's is available www.cn.ca/PDF/EDI_210_Guide.pdf  and is an example of all the fields and contains an example document as well.
    Good luck!
    Edited by: Jereme Chapman on Aug 7, 2008 5:48 PM

Maybe you are looking for

  • ADOBE Interactive Form not getting displayed in Browse

    Hi, Currently I am working on EhP4 project on ECC 6.0 environment. For HCM, We have interactive ADOBE forms for MSS. While testing we found that all buttons are displayed in a browser (we are are window 7 IE 8 ) but interactive form is not getting di

  • DPS App Builder - Can't create ipa or zip files

    Hello, I'm following this guide : http://help.adobe.com/en_US/ppcompdoc/Step_by_step_guide_to_dps_se.pdf But I'm stack on page 55 between number 6 and 7. The program download my files, and change for this message (FR sorry) : So it look like it finni

  • T60P cannot download drivers / connect to proper wireless

    I got a new hard drive for my T60P, so I am trying to install Windows XP on it. I got the computer through govconnection, so it never came with a recovery disk; now I am trying to install a clean version and install all the drivers manually, and it i

  • Where-used for a function module

    All,    I have a function module used in several update and transfer rules.  I would like to know EVERY place it is used.  The 'Where-used' button returns not found, even though I know it is used in several places.  I am on 3.5,  Is there any way to

  • Wireless guest users cannot ping if ACL is applied

    Hi friends, This is the first time I am trying my hands on wireless gears. I have 2500 WLC and 1142 AP (which I converted from Standalone to LAP). I have a layer 3 POE switch where i am using port 1 for the WLC which is a trunk port. Port 2 is for th