IDOC settings and monitoring transactions-

Hi gurus,
What are the settings in customizing and in easy access to send a PO via EDI to a vendor?
Regards,
Deepak.

1. You must maintain an e-mail address in the address in the vendor master.
2. The same applies to your own user master. You also have to specify an e-mail address there in order to identify the sender.
Note that it is not possible to change the e-mail address of the vendor via the SAP purchase order transaction (ME21N, ME22N, and so on). The system only uses the e-mail address of the vendor that is maintained in the vendor master!
3. For the output type for default values, a communication strategy needs to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the Customizing via the following path: (SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy). As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).
4. Use the standard SAP environment (program 'SAPFM06P', FORM routine 'ENTRY_NEU' and form 'MEDRUCK') as the processing routines.
5. In the condition records for the output type (for example, Transaction MN04), use medium '5' (External send).
6. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.
7. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.

Similar Messages

  • Provide ALE and IDOC Faqs and all Transactions

    Dear Experts,
    I am new to ALE & IDOC.
    Please provide ALE & IDOCs FAQs and all Transactions?
    Thanks in advance.

    <b>FAQS</b>
    A L E
    Q: Our IDOC remains in status 51 ( not posted) while testing ALE setup by passing DEBMAS02 Idocs. The message 'Field KNA1-BRSCH is not an input field'. This is the Industry key. What are we missing?
    A: Go to IMG - menu path IMG->LogisticsGeneral-> Logistics Basic Data: Business partners->Customers-> Control->Define Account groups and field selection for customer.
    Select sold-to or ship-to. Select General Data. Select control and double click. Industry key is found here. Change the option to 'Optional Entry'.
    Check OSS 5599. You may have to update view V_T078D also.
    E D I / IDOC
    Q:1 We created an EDI Vendor and created all required output conditions. However no IDOC is generated when PO is printed. Why?
    A: Go to Header->output for the PO. The output type shall be '6'. The status shall be '1'. If the status is '0' check the timing. If the status is '2' , go to 'GOTO->Processing Log' and the explanation for non-generation of IDOC can be seen.
    Q: How can we create / upload IDOC's from legacy system to SAP?
    A: Third party tool Mercator may be used to convert Legacy files to Idoc format. Mercator provides an IDOC tree import facility, SAP provides the export facility. You can transfer the Idoc layouts from SAP to Mercator automatically and then map.
    Q: We want to receive an outbound EDI 855 IDOC only if E2EDP20 -scheduling confirmation segment is present. Else get an "error" status preventing triggering the EDI subsystem.
    A: User exit logic has to be added in function IDOC_INPUT_ORDRSP.
    Set up a test flag and set it off when the IDOC header is read.
    Turn the flag ON when the EDP20 segment is read.
    Interrogate this flag when the next segment after EDP20 in the same IDOC comes in. If it is on ,you have an EDP20 coming in.
    Issue an error status 51 with suitable message for whichever condition you don't want the IDOC to be processed, This will stop the IDOC from posting.
    Q: Where ever PO is sent to the vendor via EDI, we want an acknowledgement of the PO by vendor. Which fields are updated and what should be my procedure?
    A: Execute Program: IDOC_INPUT_ORDRSP
    Process code: ORDR
    Message type: ORDRSP
    IDOC: ORDERS01
    The confirmation process allows the supplier to return an acknowledgment. Only Dates and quantities can be changed The information is stored in the PO and can be viewed via Item->Confirmation->Overview. The PO can be flagged as 'confirmation required' so that Pos without acknowledgement receipt can be monitored. Control keys and tolerances (days and quantities) have to be customized.
    Outbound:
    Step 1. Application document is created when transaction is saved.
    2. Message control is invoked.
    3. Messages are processed by system.
    4. Messages are Edited (if desired).
    5. Output (ALE / EDI) is checked
    6. Validate against Message control record from Partner Profile
    7. Application Document is saved.
    8. Entry NAST table is created for every selected output program
    along with Medium & Timing.
    9. Check for Process Immediately .
    If (yes)
    Determine Processing Program from TNAPR Table.
    ELSE
    Execute RSNASTED Program.
    10. Read Partner Profile to determine Process Code.
    11. Process Code points to the Function Module & Invoked.
    12. IDoc is generated.
    13. Check for ALE Request.
    if (Yes)
    Perform Filters, Conversions, Version Changes etc.
    Else.
    IDoc is stored in DATABASE.
    INBOUND:
    Step 1. EDI Subsystem creates an IDoc file from EDI Messages
    2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
    3. Data in Control Record is validate against the Partner Profile.
    4. IDoc is generated in Database and syntax check is carried out.
    5. IDoc file is deleted once file read.
    6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
    7. Check for Process Immediately.
    If NO
    Execute RBDAPP01 Program
    Else
    Read Process Code from Partner Profile
    Process Code Points to Function Module
    Application Document Posted.
    further help:
    check url
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/ale/configuration.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapdevelopment.co.uk/training
    And also u can get lots of inof from the below link.
    http://www.sapgenie.com/ale/why_ale.htm
    Just follow the procedure
    Sending System(Outbound ALE Process)
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ? Create Model View
    Tcode BD82 ? Generate partner Profiles & Create Ports
    Tcode BD64 ? Distribute the Model view
    Message Type MATMAS
    Tcode BD10 ? Send Material Data
    Tcode WE05 ? Idoc List for watching any Errors
    Receiving System(Inbound ALE )
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ? Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 ? Idoc List for inbound status codes
    ALE IDOC Steps
    Sending System(Outbound ALE Process)
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Create Model View
    Tcode BD82 !V Generate partner Profiles & Create Ports
    Tcode BD64 !V Distribute the Model view
    This is Receiving system Settings
    Receiving System(Inbound ALE )
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 !V Idoc List for inbound status codes
    Message Type MATMAS
    Tcode BD10 !V Send Material Data
    Tcode WE05 !V Idoc List for watching any Errors
    STEP 1)a Goto Tcode SALE
    Click on Sending & Receiving Systems-->Select Logical Systems
    Here Define Logical Systems---> Click on Execute Button
    go for new entries
    -System Name : ERP000
    -Description : Sending System
    -System Name : ERP800
    -Description : Receiving System
    press Enter & Save
    it will ask Request
    if you want new request create new Request orpress continue for transfering the objects
    B) goto Tcode SALE
    Select Assign Client to Logical Systems-->Execute
    000--> Double click on this
    Give the following Information
    -Client : ERP 000
    -City :
    -Logical System
    -Currency
    -Client role
    Save this Data
    Step 2) For RFC Creation
    Goto Tcode SM59-->Select R/3 Connects
    Click on Create Button
    RFC Destination Name should be same as partner's logical system name and case sensitive
    to create the ports automatically while generating the partner profiles
    give the information for required fields
    RFC Destination : ERP800
    Connection type: 3
    Description
    Target Host : ERP000
    System No:000
    lan : EN
    Client : 800
    User : Login User Name
    Password:
    save this & Test it & RemortLogin
    STEP 3) Goto Tcode BD64 -- click on Change mode button
    click on create moduleview
    short text : xxxxxxxxxxxxxx
    Technical Neme : MODEL_ALV
    save this & Press ok
    select your just created modelview Name :'MODEL_ALV'.
    goto add message type
    Model Name : MODEL_ALV
    sender : ERP000
    Receiver : ERP800
    Message type :MATMAS
    save & Press Enter
    STEP 4) Goto Tcode BD82
    Give Model View : MODEL_ALV
    Partner system : ERP800
    execute this by press F8 Button
    it will gives you sending system port No :A000000015(Like)
    STEP 5) Goto Tcode BD64
    select the modelview
    goto >edit>modelview-->distribute
    press ok & Press enter
    STEP 6) goto Tcode : BD10 for Material sending
    Material : mat_001
    Message Type : MATMAS
    Logical System : ERP800
    and Execute
    STEP 7)goto Tcode : BD11 for Material Receiving
    Material : 100-300
    Message Type : MATMAS
    and Execute --> 1 request idoc created for message type Matmas
    press enter
    Here Master Idoc set for Messge type MATMAS-->press Enter
    1 Communication Idoc generated for Message Type
    this is your IDOC
    Change Pointers
    how to change the description of a material using ALE Change Pointers.
    I will give the following few steps
    1) Tcode BD61---> check the change pointers activated check box
    save and goback.
    2) Tcode BD50---> check the MATMAS check box save and comeback.
    3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
    4) Tcode BD52---> give message type : matmas press ok button.
    select all what ever you want and delete remaining fields.
    save & come back.
    5) 5) go to Tcode MM02 select one material and try to change the description and save it
    it will effects the target systems material desciption will also changes
    6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
    give Message type : MATMAS and Executte
    ALE/IDOC Status Codes/Messages
    01 Error --> Idoc Added
    30 Error --> Idoc ready for dispatch(ALE Service)
    then goto SE38 --> Execute the Program RBDMIDOC
    29 Error --> ALE Service Layer
    then goto SE38 --> Execute the Program RSEOUT00
    03 Error --> Data Passed to Port ok
    then goto SE38 --> Execute the Program RBDMOIND
    12 Error --> Dispatch ok
    Inbound Status Codes
    50 Error --> It will go for ALE Service Layer
    56 Error --> Idoc with Errors added
    51 Error --> Application Document not posted
    65 Error --> Error in ALE Service Layer
    for 51 or 56 Errors do the following steps
    goto WE19 > give the IDOC Number and Execute>
    Press on Inbound function Module
    for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
    ALE/ IDOC
    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
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    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
    http://www.allsaplinks.com/idoc_sample.html
    <b>Reward Points if it helps,</b>
    Satish

  • Power Settings, computer and monitor will not go to sleep

    My computer and monitor will not go into sleep mode enventhough I have the power options set to do so in 30 minutes

    Hello @Andrea1023,
    Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
    I understand that your computer is not going into sleep mode when it is supposed to, but before and you require assistance. I would be happy to assist you, but first I would encourage you to post your product number for your computer. I am linking an HP Support document below that will show you how to find your product number. As well, if you could indicate which operating system you are using. And whether your operating system is 32-bit or 64-bit as with this and the product number I can provide you with accurate information.
    How Do I Find My Model Number or Product Number?
    Which Windows operating system am I running?
    Is the Windows Version on My Computer 32-bit or 64-bit?
    Please re-post with the requested information and I would be happy to provide you with assistance. Thank you for posting on the HP Forums. Have a great day!
    Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
    Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
    Dunidar
    I work on behalf of HP
    Find out a bit more about me by checking out my profile!
    "Customers don’t expect you to be perfect. They do expect you to fix things when they go wrong." ~ Donald Porter

  • XI and SAP --- & transactions

    HELLO EVERYONE,
    i have very stupid question with me but then also wanted to clear it.
    when i login in XI i have tcodes to do specific tasks and same is with any r/3 system.
    My doubt is with the IDOC list which we see in the XI side, e.g when i give we02 then it will give me IDOC list and same is with the SAP R/3 system also.
    Why XI has all these transactions ? when do we need to use we02 in XI??
    thanks,
    gaurav
    Message was edited by:
            gaurav sharma

    HI
    Below are the complete T-CODES which we use in SAP XI.
                 COMPLETE SAP XI TRANSACTION CODES
    ALRTCATDEF- Alerts Configuration.
    ALRTDISP - Display of Alerts Created
    SXMB_IFR -> Start Integration Builder
    SXMB_MONI -> Integration Engine - Monitoring
    SXI_MONITOR -> XI: Message Monitoring
    SXI_CACHE ->   To Access IS runtime cache
    SXI_SUPPORT -> Test all the Repository and Directory Objects
    SXI_CACHE -> XI data directory cacheidx1 -> idoc adapter
    IDX2 -> idoc metadata
    IDX5 -> monitocr idoc adapter
    SM21 -> log di sistema
    ST22 -> dump abap (analisi di eccezioni)
    SMQ1 -> messages inbound e outbound queue
    SMQ2 -> messages inbound e outbound queue
    SMICM -> J2EE administration
    ST06 -> stato della macchina cpu memory filesystem machine status - cpu, memory and file system.
    ST03 -> workload.
    SCC4 -> visualizza mandanti del sistema
    WE20 -> partner profiles
    sale - ale settings
    RZ10 - edit system profile
    SM59 ->mantain rfc destinations
    BD64 -> mantain distribution model (trasformazioni)
    SU01 -> users
    AL08 -> list all logged users(user login logon)
    SE10 -> Change Request
    SE09 -> Change Request
    WE05 -> All idocs
    WE19 -> IDoc Test Tool
    WE21 -> port definition
    SE11 -> Data dictionary
    SM21 -> log sistema xi
    se37 -> mantain funcion modules
    SICF -> http server configuration
    SMGW -> trace, alzare livello di trace.
    BD13 ->
    BD64 -> modelli di distribuzione
    PFCG -> Roles
    tabella TSTC -> sap transactions codes
    tabella TSTCT -> transaction descriptions
    STMS -> transports management
    SPAM -> apply ABAP support packages
    SPAU -> manage objects after apply support packages
    SE01 -> manage change requests
    SLDCHECK -> Test SLD Connection
    SLDAPICUST-> SLD API Customizing
    SXMB_ADM -> Integration Engine - Administration
    SXMB_MONI_BPE -> Process Engine - Monitoring
    SE38 -> ABAP Editor
    SE11 -> ABAP Dictionary
    ST22 -> ABAP dump analysis
    SPROXY-> ABAP Proxy Generation
    SE80 -> Object Navigator
    ABAPDOCU -> ABAP Documentation and Examples
    SE24-> Class Builder
    SM21-> Online System Log Analysis
    SMQ1-> qRFC Monitor (Outbound Queue)
    SMQ2-> qRFC Monitor (Inbound Queue)
    RZ70-> SLD Administration
    SM58-> Asynchronous RFC Error Log
    SM59-> RFC Destinations (Display/Maintain)
    SMICM-> ICM Monitor
    WE60-> Documentation for IDoc types
    BD87-> Status Monitor for ALE Messages
    IDX1-> Port Maintenance in IDoc Adapter
    IDX2-> Meta Data Overview in IDoc Adapter
    WE05-> IDoc Lists
    WE02-> Display IDoc
    WE19-> Test tool
    WE09-> Search for IDocs by Content
    WE20-> Partner Profiles
    WE21-> Port definition in XI
    SE16-> Data Browser
    SE93-> Maintain Transaction Codes
    SM30-> Call View Maintenance
    SU01-> User Maintenance
    SM02-> System Messages
    BD54 -Logical System Creation.
    SWXF_PBUILDER -> for Detail BPM Process
    SMQS - > to register the destination in QOUT scheduler
    WEOUTQUEUE - > to start the queue processing
    SMQR - > to register the queue
    IDXPW - > to activate the IDOC message package
    IDXP - > to monitor the message packages.
    SWF_XI_CUSTOMIZING -> transaction to check prerequisites for integration processes
    Reward with points if found useful
    cheers

  • Difference btw idoc ale and edi

    Hi all,
    I'm a beginner in abap, can anyone send me the concepts of ALE, IDOC and EDI and the difference btw all the three.
    Also do send some materials for the same.

    Hi,
    ALE (Application Linking and Enabling)
    Ale Technology is SAP’s technology to support distributed yet integrated processes across several SAP systems.
    Distributed Process:
    A distributed process is one in which part of a business process is carried out on one system and part on another. The two systems would exchange data with each other at appropriate points to stay synchronized.
    Need for Distributed Process:
    • Business in Different Geographical Locations.
    • Non availability of dedicated network.
    • Cultural and language differences in Geographical locations.
    • Running of Mission-critical Applications (Like Maintenance downtime etc.).
    • Separate up gradation of Modules.
    Distributed SAP SYSTEM – CHALLENGES
    • A system that understands the syntax and semantics of the data. It was important from the very beginning to base the distribution of data on business rules, not on database replication techniques.
    • Distributed systems that can maintain their autonomy while being integrated as one logical SAP system. The systems should be able to operate independently and support logical processing of transactions and data.
    • Distributed systems that can handle different data models. A local implementation should be able to customize the system to meet its local needs.
    • Receiving systems that can handle their own problems and not tie up the sending system.
    • Systems that maintain continued operation in spite of network failure. Changes made to either system should be synchronized after the network connection is restored.
    • A sound technology and methodology that can be used in all distribution scenarios.
    SAP Distributed environment:
    ALE allows for efficient and reliable communication between distributed processes across physically separate SAP systems.
    ALE is based on application to application integration using messaging architecture. A message defines data that is exchanged between two processes. IDocs are containers that hold data exchanged between the two systems.
    Benefits of ALE:
    • Integration with non-SAP systems: ALE architecture allows third party applications to integrate with SAP system.
    • Reliable Distribution: Once message type created and the receiver of the message is determined, ALE delivers the message to the recipient. If there is any network problem it will buffer the message and delivers the message once the network is restored. It also ensures that the message is not delivered twice.
    • Release Upgrade: Any of the distributed system can be upgraded to the new release of SAP without affecting the functionality. The ALE layer ensures backward compatibility of messages exchanged between systems.
    ALE Architecture:
    It consists of an Outbound process, an Inbound process, and an Exception – Handling process.
    Outbound Process:
    ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
    1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
    2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
    3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
    4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
    Inbound Process:
    The inbound process receives an IDoc and creates a document in the system.
    1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
    2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
    3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
    Over view of IDocs:
    IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
    IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDoc’s definition and IDoc Data is an instance of the IDoc Type.
    IDoc Types:
    IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
    An IDoc is an instance of an IDoc Type and consists of three types of records.
    i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
    ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
    iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
    Message in IDoc Type:
    A Message represents a specific type of document transmitted between two partners.
    Outbound Process in IDocs:
    Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
    The Customer Model:
    A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
    Message control:
    Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
    Change Pointers:
    The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
    Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
    IDoc Structure:
    A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
    Selection Program:
    Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection program’s design depends on the triggering mechanism used in the process.
    Filter Objects;
    Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
    Port Definition:
    A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
    RFC Destination:
    The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
    Partner Profile:
    A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDoc’s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
    Service Programs and Configuration Tables:
    The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
    Process flow for Distributing Transactional Data:
    Transactional data is distributed using two techniques: with Message control and without message control.
    Process flow for Distributing Master Data:
    Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
    Triggering the Outbound Process via Stand-Alone Programs:
    Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
    The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
    Triggering the Outbound Process via Change Pointers:
    The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
    A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
    Processing in the Application Layer:
    The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
    Processing in the ALE Interface Layer:
    Processing in the ALE Layer consists of the following steps:
    • Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
    • IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
    • Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
    • Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
    • Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
    • Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
    • Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
    • Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc – Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch – ALE Service).
    • IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
    Processing in the Communication Layer:
    To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
    Inbound Process in IDocs:
    An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
    Posting Program:
    Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
    Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
    Workflow:
    A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
    Partner Profile;
    A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
    Process flow for the Inbound process via a Function Module:
    In this process, IDocs are received from another system and passed to the posting function module directly.
    1. Processing in the communication Layer:
    The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
    2. Processing in the ALE/EDI Interface Layer:
    • Basic integrity check: A basic integrity check is performed on the control record.
    • Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
    • Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc – Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
    • IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
    • IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
    3. Processing in the Posting Module:
    The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
    The results of execution are passed back via the function module’s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).
    IDOC:
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    [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]
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    [Re: How to create IDOC;
    Check below link. It will give the step by step procedure for IDOC creation.
    [http://www.supinfo-projects.com/cn/2005/idocs_en/2/]
    ALE/ IDOC
    [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]
    [http://www.sappoint.com/abap/ale.pdf]
    [http://www.sappoint.com/abap/ale2.pdf]
    [http://www.sapgenie.com/sapedi/idoc_abap.htm]
    [http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm]
    [http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm]
    [http://www.allsaplinks.com/idoc_sample.html]
    [http://www.sappoint.com/abap.html]
    [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]
    [http://www.allsaplinks.com/idoc_sample.html]
    [http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs]
    go trough these links.
    [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]
    [http://www.sappoint.com/abap/ale.pdf]
    [http://www.sappoint.com/abap/ale2.pdf]
    [http://www.sapgenie.com/sapedi/idoc_abap.htm]
    [http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm]
    [http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm]
    [http://www.allsaplinks.com/idoc_sample.html]
    [http://www.sappoint.com/abap.html]
    [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]
    [http://www.allsaplinks.com/idoc_sample.html]
    [http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    [http://www.allsaplinks.com/idoc_sample.html]
    [http://www.sapgenie.com/sapedi/idoc_abap.htm]
    [www.sappoint.com]
    --here u can find the ppts and basic seetings for ALE
    [http://sappoint.com/presentation.html]
    [www.sapgenie.com]
    [http://www.sapgenie.com/ale/index.htm]
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    RFC:
    RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;
    and you will be passing an Import parameter DESTINATION to it.
    Other code and usage will be similar to any fun module;
    Have a look at any fun module in SE37 to understand better about the different components of Fun modules;
    Refer this link:
    [http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm]
    check out the following link it might help you
    [http://help.sap.com/printdocu/core/Print46c/de/data/pdf/BCFESDE2/BCFESDE2.pdf]
    EDI:
    Electronic Data Interchange
    Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.
    Refer
    [http://www.erpgenie.com/sapedi/index.htm]
    [http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm]
    [https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp]
    [http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/]
    [http://www.erpgenie.com/sapedi/index.htm]
    [http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd]
    EDI FLOW :
    Here is some thing which helps you and here the purchase order is taken as example too..
    Electronic Data Interchange, or EDI, is the electronic exchange of business data. Using a standard format, EDI provides a method of transmitting business data from one computer to another, without the need to re-key data. This electronic link can result in more effective business transactions. With EDI, paper documents such as invoices can be replaced with electronic transmissions, thus time is saved, and the potential for error is minimized. Data can be exchanged at any time. Related business expenses, such as postage, printing, phone calls, and handling, can also be significantly reduced. EDI can aid in the support of manufacturing efforts, such as Just-in-Time and Third Party Warehousing, and financial efforts, such as Electronic Payments.
    What parts of the business cycle can be supported by EDI?
    Any business documents that are currently exchanged using paper can be converted to an EDI. Standards. Standards include ANSI X12 and XML/EDI are primarily used in the United States, while EDIFACT is used in Europe and Asia.
    How does EDI get started?
    EDI gets started when one company contacts another expressing interest in trading business documents electronically using Electronic Data Interchange. The two companies must first determine each other's EDI capabilities. If you do not already know your EDI capabilities, we have prepared a questionnaire to help you determine them. If you are already EDI capable, we will coordinate with your technical staff to determine a testing plan. Upon completion of testing the EDI documents, the appropriate business personnel will set a production start date to begin the exchange of EDI business data. If you are not EDI capable, we recommend you first obtain a commitment from your upper management. Your company will need to allocate resources and capital for software, hardware, testing, possible programming, and training.
    What is the flow of EDI?
    The flow of EDI depends on the sophistication of your systems and your EDI software. If you have internal purchasing/order entry systems, you will need interface programs that can extract and insert data out of and into these systems. EDI programs that interface with your internal systems are preferred over software that requires re-keying of data. Embassy Software specializes in seemless interface between EDI and your back office systems. Using a purchase order as an example of a business document your customer would send that PO electronically (850) to you. It could be sent either through a VAN (Value Added Network) or through an FTP server. You would take that 850 and convert it either into and ODBC database, a flat file or XML document to be imported into your Order System with the use of EDI Software such as PassportXchange.. Using EDI communication software, which is part of the PassportXchange package you would pull down data at set intervals from the VAN or FTP. These documents are then processed through EDI translation software and output to our order entry system. Finally, an EDI document called a functional acknowledgment (997) is sent to your customer.
    check this.
    [http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
    [http://www.sapgenie.com/sapedi/idoc_abap.htm]
    [http://www.sapgenie.com/sapedi/index.htm]
    [http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm]
    [https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp]
    [http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/]
    [http://www.erpgenie.com/sapedi/index.htm]
    [http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd]
    [ALE / IDOC / RFC / EDI]
    [SAP ABAP and EDI/ALE/IDOC]
    [Re: IDOC/BAPI/ALE/EDI]
    Regards,
    Dhruv Shah

  • IDOC to JDBC scenario-IDOC settings

    Hi all i m doing an idoc to JDBC scerio and i have configured the settings and trying to trigger an ido and see whether i am able to post the data into the Db or not but i cant see idocs in XI:these are the steps i follwed posted in earlier forums:
    •  Create an RFC destination to XI in the sender SAP system using SM59
    •  Create a transactional port to XI using the RFC destination created in the above step
    • Create a Partner agreement using transaction we20 in the sender SAP system
    • Create a logical system using transaction bd54 for the partner agreement created in the above step
    • Select an IDOC using transaction we19 and change the EDIDC header recipient port & LS name
    •  Create an RFC destination to the Sender SAP system using SM59
    • Create port to sender system using idx1 in the XI system for the RFC destination created in the above step
    • Create Metadata in idx2 transaction..
    I have done the above and trying to trigger an idoc in we19 by changing the control records...but  my idoc is not getting triggered.
    Did i miss any other configuration?Please guide me.
    also my guess is that i might have missed something in my partner profile config,
    i specified ordrsp msg type in o/b parameters,specfied the port,selected trasfer idoc immediatley option,specified process code..i guess thats about it
    Am i rite?Am I missing something.
    Thanks

    HI Aarthi,
    In WE19 while triggering Idoc, what are you getting ? ANy error..Is it created any Idoc number . If so go to WE02 and check the status ...
    If Idoc is triggered and it is not reached into XI, then you can check in SM58  for the status.
    TO cross check the configuration-
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    Also check how to guide for Idoc scenario.
    https://websmp106.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&
    Regards,
    Moorthy

  • SFDM Tool (Shop Floor Dispatching and Monitoring), Technical questions

    Hi Everybody,
    i am very excited to change knowledge here on the SCN.
    Right now I am analyzing the SFDM Tool (Shop Floor Dispatching and Monitoring) and need some more Information, which cannot be found via Internet research. I hope someone, who is familiar with the technical details can support me with answers.
    1. Master Data:
    - How does the Interchange of master data (such as machine capacities in terms of time/quantities or number of available machines) work between the       SFDM and the ERP System?
    - Is there a permanent interface between the SFDM and the master data in the ERP System?
    - If so, which of the master data are communicated?
    - Are there any limitations?
    - Do BAPIs (Business Application Programming Interface) play a role?
    - Is any further master data maintenance necessary, if the customer wants to implement SFDM?
    2. There is a backend component situated in the ERP System called "SFDM on ABAP 1.0". What is the aim of this component?
    3. Does the SFDM work with algorithms? If so, why?
    4. Does the SFDM consider other machines in the same production plant?
    5. Does it work over HANA?
    6. Any further functionalities or restrictions?

    Hi
    i wouldn't recommend SFDM for performance problem solving, if this is the issue you are facing.
    If this is because planners are "lost" with CM25 because of problems for Production Orders selection and so-on, then try SFDM.
    There is no new functionality compared to CM2x transactions within ERP.
    The benefits are clearly focused on design and user-friendliness:
    interactive logs
    easy configuration of settings and strategy compared to CM2x TCodes
    accessible details
    Please keep also in mind the fact that this is working for individual capacities (cf. Rough Guide) and related constraints in terms of capacity category (only 0001 is supported).
    Best regards.
    Pierre-Edouard

  • Data Fir  IDOC  ALE  and EDI

    Hello All,
        I am newly join in IT company (Name don't want to specify) .  They have putted me in a consolidate project in which I do have to work on IDOC,ALE and EDI object.
    yet in my career with SAP ABAP I haven't work on the above mention terms of SAP. Can some One please guide me and provide me some material to prepare my self best for the things.
    Regards
    Swati Namdev

    Some use full Tcodes:
    ALE / EDI/ IDOCS TRANSACTION CODES
    Transaction Code     Description
    WE02     List Of All Idocs Created. (Default, Additional, EDI)
    WE05     List Of  Idocs Created.    (Standard, Additional)
    WE06     Active Monitoring For Idoc Processing.
    WE07     Idoc Statistics.
    WE08     Display View u201CFile Statusu201D:Overview-Path Name.
    WE09     Idoc Search For Business Contents (Database).
    WE10     Idoc Search For Business Contents (Archive).
    WE12     Modification Of Outbound File, Triggering Inbound Processing.
    WE14     Process All Selected Idocs.
    WE15     Selection Program For Issuing Output.
    WE16     Trigger Inbound Processing.
    WE17     Trigger Status Processing.
    WE18     Generate Test Status File For Outbound Idocs.
    WE19     Test Tool For Idoc Processing
    WE20     Partner Profile.
    WE21     Ports In Idoc Processing.
    WE23     Display Test Catalog Test Idoc Interface.
    WE24     Maintain Table View. Direction-1.(Outbound)
    WE27     Maintain Table View. Direction-2.(Inbound)
    WE30     Develop Idoc Type.
    WE31     Develop Idoc Segments.
    WE32     View Development.
    WE33     Maintain Table Views.
    WE34     Change View u201CTable Of Style Ids With The Objects To Be Loadedu201D
    WE40     Display System Process Code.
    WE41     Display View: Logical Msg Overview. For Outbund.
    WE42     Display View: Logical Msg Overview. For Inbound.
    WE43     Display Status Records.
    WE44     Display Partner Types
    WE45     Maintenance Interface: Forwarding Inbound/EDILOGADR For Application
    WE46     Global Parameter For Idoc Interface.
    WE47     Status Maintenance.
    WE50     Display Text For Process Code System.
    WE54     Idoc Function Module For File Name
    WE56     Display Status Process Code
    WE57     Idoc Assignment Of FM To Log. Message And Idoc Type.
    WE58     Text For Process Code Status.
    WE60     Documentation For Idoc Type.
    WE61     Documentation For Idoc Record Type.
    WE62     Documentation For Idoc Segment Type.
    WE63     Documentation For Idoc Record Types And Idoc Types (Parser).
    WE64     Process Code In Idoc Inbound And Outbound.
    WE70     Conversion Table For Basic Types.
    WE71     Conversion Table For Extensions.
    WE72     Conversion Table For Field DOCTYP.
    WE73     Conversion Table For Logical Message Type.
    WE81          EDI:Logical Message Type.
    WE82     Message Types And Assignment To Idoc Types.
    WE84     Assignment Table Between Idoc And Application Field.
    ALE / EDI/ IDOCS TRANSACTION CODES
    Transaction Code     Description
    BD10     Send Material (Matmas)
    BD11     Get Material.
    BD12     Send Customer.
    BD13     Get Customers
    BD14     Send Vendor.
    BD15     Get Vendor.
    BD16     Send Cost Center. (Cosmas)
    BD17     Request Cost Center.
    BD18     Send G/L Accounts.
    BD19     Get Master Data G/L Accounts.
    BD20     Inbound Processing Of Idocs Ready For Transfer.
    BD21     Creating Idoc Types For Change Pointers.
    BD22     Delete Change Pointers.
    BD23     Serialization Using Time Stamp: Deletion Of Old Time Stamp.
    BD24     Send Cost Elements.
    BD25     Send Activity Type (COAMAS)
    BD26     Request  Activity Type
    BD27     Cost Center/Activity Types: Transmit Plan Quantities And Acty Prices.
    BD28     Cost Center/ Cost Elements: Send Control Records.
    BD30     Material Bom Distribution. (Bommat).
    BD31     Document Structure Distribution. (Bomdoc)
    BD32     Plant Allocation To Material Boms Distribution.
    BD33     Distribution Of Material Variants. (STTMAT)
    BD34     Distribution Of Boms (BOMORD)
    BD35     ALE: Send Business Process Group.
    BD36     ALE: Send Business Process.
    BD37     ALE: Send Business Process Price.
    BD40     Generate Idocs For Serialization Group From Change Pointers.
    BD41     Dispatch Of Idocs  Of Serialization Group.
    BD42     Check Dispatch Status Of Idocs Of Serialization Group.
    BD43     Processing Inbound Idocs Of Serialization Group.
    BD44     Change View u201CSerialization Groupu201D.
    BD47     Dependence Between Methods.
    BD48     Dependence Between Methods And Message Type.
    BD50     Activate Change Pointers For Message Type.
    BD51     Characteristics Of Inbound Function Module.
    BD52     Determine Work Area.
    BD53     Reduce Message Type.
    BD54     Change View: Logical Systems
    BD55     Idoc Conversion.
    BD56     Maintain Idoc Segment Filters.
    BD57     Link Type And Serialization Type Of Message Type.
    BD58     Convert Organizational Unit.
    BD59     Allocation Of Object Type.
    BD60     Additional Data For Message Type.
    BD61     Activate Change Pointers Generally.
    BD62     Display Conversion Rule.
    BD63     Transport Of Ale Tables For A Message Type.
    BD64     Display Distribution Model.
    BD65     Maintain Idoc Type Required Fields.
    BD66     Change Idoc Fields.
    BD67     Function Module For ALE/EDI Overview.
    BD68     Maintain List.
    BD69     Assignment Of Idoc Type To Message Type.
    BD70     Cross-System Comparison Of Number Range Objects.
    BD71     Attributes For Receiver Determination.
    BD72     Active Events For ALE/EDI
    BD73     Start Error Handling For Non-Posted Idocs.
    BD75     Status Conversion With Trfc Execution.
    BD77     Generate Transport Requests For Distributing ALE Customizing Data.
    BD78     Monitoring Ale Customizing Data Transport
    BD79     ALE IDOC Segments - Conversion Rule
    BD81     Filter Objects For BAPI Parameter Filtering
    BD82     Generating Partner Profile
    BD83     Re-Processing Incorrect Outbound Odocs.
    BD84     Re-Processing Of Idocs After ALE Input Error.
    BD85     Consistency Check: Reassignment Between Two System.
    BD86     ALE Consistency Check: Create Purchase Order From Sales Order.
    BD87     Select Idocs
    BD89     Customizing Data Modeling For Distribution Model.
    BD91     Distribute All Characteristics Via ALE.
    BD92     Distribute Class Via ALE: Send Direct.
    BD93     Distribution Of Classification Data Via ALE.
    BD95     Ale Object View
    BD96     Filter Object For Receiver Determination Of Methods.
    BD97     Assign RFC Destination For Synchronous Method Calls.
    BD98     Consistency Check With Workflow Link
    BD99     Dependencies Between Message Types.
    BD100     Display Serialized Idocs. (Serialization Using Object Types)
    BD101     Serialization Using Object Types: Consistency Check.
    BD102     Ale: Outbound Channel Registry.

  • XI Monitoring transaction code

    Dear Consultant
    I am new in XI . I am upgradting my skill, can any one help and send me the list of XI monitoring transaction code and some valuable document which help me to upgrade myself as a XI administrator.
    Regards
    Vimal Pathak

    Hi,
    Also check these:
    sxmb_ifr-- launch integration builder/ configuration
    Proxy Generation
    SPROXY--Proxy generation
    Monitering features:
    sxmb_moni-- monitering of messages
    SXMB_MONI_BPE--Business process monitering
    SXMS_SAMON--- monitor for sync-async communication
    Adminsitration of XI
    sxmb_adm-- Administration
    QUEUE MONITORING
    SMQ1 Outbound queue
    SMQ2 Inbound Queue
    IDoc's& RFC's related
    idx1, idx2 for IDoc meta data
    SM58--RFC error Log
    Others
    SWELS---Event trace switching on and off.
    SXI_MAPPING_TEST To test mappings
    SXI_CACHE To check directory cache
    Regards,
    Subhasha Ranjan
    Reward points for  helpful answer. *

  • Idoc Configuration and interfaces related to 810

    Hi,
      Can any one tell me the entire configuration of ALE and EDI810 supported tools?
    Thanks
    Shobi

    <b>Hi,
    ALE
    To develop a new custom ALE scenario, comprises 5 steps:
    1.     Design and develop the custom IDoc with it’s segments and a new message type
    2.     Configure the ALE environment with the new IDoc and message type (customer model, partner profiles and linking IDoc to message type)
    3.     Develop the outbound process which does the following:
    •     Populates the custom IDoc with control info and functional data
    •     Sends the IDoc to the ALE layer for distribution
    •     Updates status and handles errors
    4.     Configure the ALE inbound side (partner profiles with inbound process code)
    5.     Develop the inbound process which does the following:
    •     Reads the IDoc into a BDC table; selects other data that is required
    •     Runs transaction using call transaction or BDC session
    •     Updates status and handles errors
    Below is a pictorial representation of the flow of a complete ALE scenario from the sending system to the receiving system.
    Figure 1: ALE Scenario model
    1.1.     ALE Example
    For the purposes of this example we will develop a small ALE scenario. This scenario is described below.
    “The receiver of an internal service must be able to reverse (cancel) the invoice receipt which will then cancel the applicable billing document automatically on the service provider’s system.”
    Figure 2: Example Purchasing & Selling scenario
    We will develop a custom IDoc to carry the billing number from the Service Receiver’s system to the Service Provider’s system. We will populate the IDoc in a user exit on the sending side and we will process the transaction on the receiving side using a custom function module and a BDC transaction call.
    No rule conversion, segment filtering or version conversion will be implemented in the model as described in Figure 1.
    Requirements
    •     Working ALE environment - See ALE Basis Configuration Guide;
    •     ALE scenario design together with the business requirement;
    •     Development access; and
    •     ALE configuration access.
    NOTES:
    1.     All IMG references to transactions are located in the transaction SALE which is the ALE portion of the IMG
    2.     This is one way of developing a scenario where no message control exists. If message control exist (EG. On purchase orders) then NAST can be used to call an outbound function module that would create the required IDocs.
    3.     Extensive knowledge of IDocs and ALE basis configuration is required in order to understand this guide.
    2.     OUTBOUND PROCESSING
    2.1.     Create IDoc type (WE30) Client independent
    The IDoc type refers to the IDoc structure that you will require for your development. In our case the IDoc type is called ZINVRV01. This IDoc type will have 1 segment called Z1INVRV with 2 fields, LIFNR & XBLNR, in this segment. If you require many segments or nested segments then they are also created using the same procedure.
    We will create the IDoc of the following structure:
    ZINVRV01
    Purchasing and Selling - Invoice receipt reversal
    Z1INVRV     P&S - Segment 1
         Segment fields     
              LIFNR     Vendor account number
              XBLNR     Reference document number
    Figure 3: IDoc type ZINVRV01
    To create the IDoc type, follow these next few steps:
    •     Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
    •     Type in ZINVRV01 and click on Basic IDoc type, click the Create icon
    •     Click on Create new (we are creating an IDoc from scratch but you may want to copy another IDoc if it is similar to your requirements) and enter a description, and press enter
    •     Click on ZINVRV01 and then on the Create icon
    •     Enter Z1INVRV as the segment type (must start with Z1), check mandatory if the segment must exist (in this case check it), enter 1 in minimum number and 1 as maximum number. (Make the maximum number 9999999999 if there are going to be many of these segments in each IDoc. IE. When line items are passed via IDocs), click on Segment editor
    •     Enter a description for your segment type and create
    •     Enter a description for your segment, enter each field required in your IDoc, in our case type LIFNR across for Field name, DE structure and DE documentation, repeat for XBLNR and press enter to validate.
    •     Save and generate, press back
    •     To release the segment choose Goto, Release from the menu
    •     Check the box on the line of your new segment
    •     Save, back and enter
    •     Your IDoc type structure should be displayed with your new segment
    •     Save and back
    •     To release the IDoc type choose Extras, Release type from the menu and Yes
    Your IDoc is now ready for use. If you need to add fields or segments to your IDoc type, you will need to cancel the release of the IDoc type as well as the segment release using a similar procedure followed above (except now you uncheck the release box for the segment and you choose cancel release for the IDoc type).
    2.2.     Create message type (WE81) Client independent
    To create a new message type, follow these next few steps:
    •     Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
    •     Choose Create logical message type by double clicking on it
    •     Click on change icon to enter change mode
    •     Click on New entries to add a new type
    •     Enter the required message type, in our case it is ZINVRV and an appropriate description
    •     Save and exit.
    Your message type has now been created. The next step will be to link it to the IDoc.
    2.2.1.     Link message to IDoc type (WE82 & BD69) Client independent
    To link the message type to the IDoc type follow these next few steps:
    •     Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
    •     Click on change icon to enter change mode
    •     Click on New entries to create the link
    •     Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
    •     Save and exit
    •     Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
    •     Click on change icon to enter change mode
    •     Click on New entries to create the link
    •     Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
    •     Save and exit
    Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
    2.2.2.     Maintain object type for message type (BD59) Client independent
    The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
    For our own message type and IDoc you must maintain object types for the links.
    If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
    To add an object type to our message type, follow these next few steps:
    •     Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
    •     Type in your message type ZINVRV and press enter
    •     Click on New entries
    •     Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
    •     Save and exit.
    You have now created an object that we’ll use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
    We now need to add our new message type to the distribution model.
    2.3.     Configuring the Distribution Model
    This task is performed on your ALE reference client.
    2.3.1.     Manual Configuration (BD64) Client dependent
    To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
    •     Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
    •     Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
    •     Choose the receiving systems to which the sending system must forward message type ZINVRV to.
    •     For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
    •     Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
    •     Save the entries.
    NOTES:
    You cannot maintain a message type between the same sender and receiver in more than one customer distribution model.
    Only the owner is authorised to modify the model.
    To change the owner of a model, choose the 'Maintain ownership of customer distribution model' function. Make sure that all changes will be distributed to all systems that know the corresponding model. To do so, you can use the correction and transport system.
    To transport the customer distribution model you should use the Distribute customer model function of the IMG as described below.
    2.3.2.     Distribute customer model (BD71) Client dependent
    After the customer model has been created centrally, it must be distributed to the other remote systems. This entails first of all setting up the communication for the distributed systems and then sending the model.
    2.3.2.1.     Distribute Model (BD71) Client dependent
    This task is performed on your ALE reference client. To distribute the customer distribution model, read the ALE configuration procedure and follow these steps:
    •     Make the settings for the communication with the other decentral systems, you have not set them yet.
    •     Define the RFC destination for R/3 connections whose names correspond to the name of the corresponding logical system.
    •     Create the output partner profile.
    •     Distribute the customer model
    •     Specify the name of the customer model.
    •     You must specify the target system to which you want to distribute the customer model.
    •     You must repeat this function for every distributed logical system.
    2.3.2.2.     Maintain sending system partner profile (WE20) Client dependent
    With this function, you define the partner profiles for all outbound and inbound messages on the basis of the customer distribution model.
    After you have defined and distributed the customer model, you will have to maintain the partner profiles locally. To do this read the ALE configuration procedure.
    •     Enter the output mode (background, immediately) and the package size for outbound processing.
    Requirements
    •     The customer model must be maintained.
    •     RFC destinations must be maintained.
    •     The customer model must be distributed.
    •     To ensure that the appropriate persons in charge are informed if a processing error occurs, you must make settings in: Error processing Maintain organisational units.
    2.4.     Populate & distribute IDoc using ABAP
    An IDoc consists of a control record with structure edidc and one or more data records with structure edidd. The control record contains the sender and recipient of the IDoc, as well as information on the type of message.
    To be able to pass an IDoc to the ALE layer, you must set up a field string with structure edidc and an internal table with structure edidd. They are used to call function module master_idoc_distribute, which performs the save to the database and triggers the dispatch if necessary.
    2.4.1.     Example code
    The code displayed below does the following:
    •     populates our IDoc segment Z1INVR with the 2 fields XBLNR and LIFNR, populates the segment name and appends this to an internal table used to store the IDoc data;
    •     populates the control record info with the message type and IDoc type; and
    •     calls the MASTER_IDOC_DISTRIBUTE function module which distributes the IDoc as configured in the customer distribution model.
    *--- Data declaration statements
    DATA:          C_INVREV_SEGNAME(7) TYPE C VALUE 'Z1INVRV',
              C_INVREV_MESTYPE(6) TYPE C VALUE 'ZINVRV',
              C_INVREV_IDOC_TYPE(8) TYPE C VALUE 'ZINVRV01',
              Z1INVRV LIKE Z1INVRV,
              C_INVREV_DOCTYPE LIKE BKPF-BLART VALUE 'YY',
              IDOC_CONTROL LIKE EDIDC,
              T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
              IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE.
    *--- Move the document header into a structure
    LOOP AT DOC_HEAD_TAB INTO DOC_HEAD.
    ENDLOOP.
    *--- Move the document item data into a structure
    LOOP AT DOC_ITEM_TAB INTO DOC_ITEM WHERE NOT ( LIFNR IS INITIAL ).
    ENDLOOP.
    *--- Populate the IDoc segment’s field with the required data
    CLEAR Z1INVRV.
    Z1INVRV-LIFNR = DOC_ITEM-LIFNR.          “Store vendor number for filter
    Z1INVRV-XBLNR = DOC_HEAD-XBLNR.          “Billing number
    IDOC_DATA-SEGNAM = C_INVREV_SEGNAME.     “Segment name
    IDOC_DATA-SDATA = Z1INVRV.               “Segment data
    APPEND IDOC_DATA.                    “Populate IDoc internal table
    *--- Move the control data info required for the distribution
    IDOC_CONTROL-MESTYP = C_INVREV_MESTYPE.
    IDOC_CONTROL-DOCTYP = C_INVREV_IDOC_TYPE.
    *--- Call the distribute function with the required parameters
    CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' IN UPDATE TASK
              EXPORTING
                   MASTER_IDOC_CONTROL          = IDOC_CONTROL
              TABLES
                   COMMUNICATION_IDOC_CONTROL     = T_COMM_CONTROL
                   MASTER_IDOC_DATA               = IDOC_DATA
              EXCEPTIONS
                   ERROR_IN_IDOC_CONTROL               = 1
                   ERROR_WRITING_IDOC_STATUS          = 2
                   ERROR_IN_IDOC_DATA               = 3
                   SENDING_LOGICAL_SYSTEM_UNKNOWN      = 4
                   OTHERS                         = 5.
    Figure 4: Outbound processing example code
    NOTE:
    For debugging purposes, use transaction WE05 (IDoc overview) to see check your IDoc status, or to see whether an IDoc was created/
    3.     INBOUND PROCESSING
    3.1.     Create Function Module
    This function module is called when a message type, of type ZINVRV, comes into the receiving system. This needs to be configured and is dealt with later in this section. The function module is passed the IDoc as a parameter.
    Example parameters
    Import parameters     Reference field     Opt Y/N
    INPUT_METHOD     BDWFAP_PAR-INPUTMETHD     N
    MASS_PROCESSING     BDWFAP_PAR-MASS_PROC     N
    Export Parameters     Reference field     Opt Y/N
    WORKFLOW_RESULT     BDWFAP_PAR-RESULT     N
    APPLICATION_VARIABLE     BDWFAP_PAR-APPL_VAR     N
    IN_UPDATE_TASK     BDWFAP_PAR-UPDATETASK     N
    CALL_TRANSACTION_DONE     BDWFAP_PAR-CALLTRANS     N
    Table Parameters     Reference field     Optional Y/N
    IDOC_CONTRL     EDIDC     
    IDOC_DATA          EDIDD     
    IDOC_STATUS     BDIDOCSTAT     
    RETURN_VARIABLES     BDWFRETVAR     
    SERIALIZATION_INFO     BDI_SER     
    Exceptions
    WRONG_FUNCTION_CALLED
    Example code
    The code displayed below does the following:
    •     populates a BDC table with the IDoc info;
    •     calls the transaction via a BDC call; and
    •     updates the IDoc status according to the BDC error status.
    EXTRACT FROM: Z_IDOC_INPUT_ZINVRV
    *--- Declaration of local variables
    DATA: C_SEGNAM(10) TYPE C VALUE 'Z1INVRV'.
    *-Loop through the IDOCs
    LOOP AT IDOC_CONTRL.
    *---Loop through the data for the IDOC
         LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.
              CASE IDOC_DATA-SEGNAM.
                   WHEN C_SEGNAM.
    *                    Here we get the info from the idoc table
                        IT_Z1INVRV = IDOC_DATA-SDATA.
              ENDCASE.
              PERFORM REV_INV.
         ENDLOOP.
         PERFORM UPDATE_IDOC_STATUS.
    ENDLOOP.
    FORM REV_INV               "Reverse invoice form
    *--- Local variables & constants
    DATA: C_TCODE LIKE BKPF-TCODE VALUE 'VF11'.  "BDC transaction code
    *--- Now we can build the bdc table to call the reversal transaction start of screen 109
    CLEAR BDC_TAB.
    BDC_TAB-PROGRAM  = 'SAPMV60A'.
    BDC_TAB-DYNPRO   = '109'.
    BDC_TAB-DYNBEGIN = 'X'.
    APPEND BDC_TAB.
    *--- Document number
    CLEAR BDC_TAB.
    BDC_TAB-FNAM = 'KOMFK-VBELN(01)'.
    BDC_TAB-FVAL = IT_Z1INVRV-XBLNR.     "Billing document number
    APPEND BDC_TAB.
    *--- OK Code for screen 109
    CLEAR BDC_TAB.
    BDC_TAB-FNAM = 'BDC_OKCODE'.
    BDC_TAB-FVAL = 'SICH'.
    APPEND BDC_TAB.
    *--- Now we can call transaction 'VF11' with the populated bdc table. The transaction is called inside the idoc-contrl loop, so a transaction will be called for every idoc (journal). the transaction is called in no-display mode ('N') because this code runs in background as it is called by ale.  The update is specified to be synchronous ('S') because we have to wait for the result to update the idoc status correctly.
    CALL TRANSACTION C_TCODE USING BDC_TAB MODE 'N' UPDATE 'S'.
    *--- Store the return code for use in another form (status update)
    RETURN_CODE = SY-SUBRC.
    *--- Here we check the return code, if there was an error, we put the transaction in a bdc session for the user to review and correct.
    IF SY-SUBRC NE 0.
         CALL FUNCTION 'BDC_OPEN_GROUP'
              EXPORTING
                   CLIENT = SY-MANDT
                   GROUP  = 'ZINVRV'
                   USER   = C_ALE_USER
                   KEEP   = 'X'.
         CALL FUNCTION 'BDC_INSERT'
              EXPORTING
                   TCODE     = C_TCODE
              TABLES
                   DYNPROTAB = BDC_TAB.
         CALL FUNCTION 'BDC_CLOSE_GROUP'
              EXCEPTIONS
                   NOT_OPEN    = 1
                   QUEUE_ERROR = 2
                   OTHERS      = 3.
    ELSE.                              "No problems
         C_EXISTS = 'N'.
      Select from the billing document table to get sales doc number
         SELECT * FROM VBRP WHERE VBELN = IT_Z1INVRV-XBLNR.
        Select from the sales document table to get user status number
              SELECT SINGLE * FROM VBAP WHERE VBELN = VBRP-AUBEL AND
                   POSNR = VBRP-AUPOS.
        Select from the status table to change the user status to pending
              SELECT * FROM JEST WHERE OBJNR = VBAP-OBJNR AND
                   STAT LIKE C_USER_STATUS.
                   IF JEST-STAT = C_US_PENDING.   "User status is pending
                        JEST-INACT = C_UNCHECKED.    "Make pending the active status
                        UPDATE JEST.
                        C_EXISTS = 'Y'.            "I.E. An entry is already in table
                   ELSEIF JEST-INACT = C_UNCHECKED AND JEST-STAT NE C_US_PENDING.
                        JEST-INACT = C_CHECKED.      "Make everything else inactive
                        UPDATE JEST.
                   ENDIF.
              ENDSELECT.
              IF C_EXISTS = 'N'.    "I.E. Pending has never been a status before
                   JEST-OBJNR = VBAP-OBJNR.
                   JEST-STAT  = C_US_PENDING.
                   JEST-INACT = C_UNCHECKED.      "Make pending the active status
                   INSERT JEST.
              ENDIF.
         ENDSELECT.       "Select from VBRP (Billing document table)
    ENDIF.
    ENDFORM.                               " REV_INV
    FORM UPDATE_IDOC_STATUS.                                              
    *--- Now we check the CALL TRANSACTION return code and set IDOC status
         CLEAR IDOC_STATUS.                                                  
         IF RETURN_CODE = 0.                                                 
              WORKFLOW_RESULT = '0'.                                            
              IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.                          
              IDOC_STATUS-STATUS = '53'.                                        
              IDOC_STATUS-UNAME = SY-UNAME.                                     
              IDOC_STATUS-REPID = SY-REPID.                                     
              IDOC_STATUS-MSGTY = SY-MSGTY.                                     
              IDOC_STATUS-MSGID = SY-MSGID.                                     
              IDOC_STATUS-MSGNO = SY-MSGNO.                                     
              IDOC_STATUS-MSGV1 = SY-MSGV1.                                     
              IDOC_STATUS-MSGV2 = SY-MSGV2.
              IDOC_STATUS-MSGV3 = SY-MSGV3.                        
              IDOC_STATUS-MSGV4 = SY-MSGV4.                        
              RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.       
              RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.    
              APPEND RETURN_VARIABLES.                             
         ELSE.                                                  
              WORKFLOW_RESULT = '99999'.                           
              IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.             
              IDOC_STATUS-STATUS = '51'.                           
              IDOC_STATUS-UNAME = SY-UNAME.                        
              IDOC_STATUS-REPID = SY-REPID.                        
              IDOC_STATUS-MSGTY = SY-MSGTY.                        
              IDOC_STATUS-MSGID = SY-MSGID.                        
              IDOC_STATUS-MSGNO = SY-MSGNO.                        
              IDOC_STATUS-MSGV1 = SY-MSGV1.
              IDOC_STATUS-MSGV2 = SY-MSGV2.                         
              IDOC_STATUS-MSGV3 = SY-MSGV3.                         
              IDOC_STATUS-MSGV4 = SY-MSGV4.                         
              RETURN_VARIABLES-WF_PARAM = 'ERROR_IDOCS'.            
              RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.     
              APPEND RETURN_VARIABLES.                              
         ENDIF.                                                  
         APPEND IDOC_STATUS.                                     
    ENDFORM.                               " UPDATE_IDOC_STATUS
    Figure 5: Inbound processing example code
    3.1.1.     Debugging inbound FM
    Use transaction WE19 to test inbound function module in debugging mode. Also use WE05 to view the IDocs and their statuses.
    3.2.     Maintain ALE attributes
    The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.
    3.2.1.     Link Message Type to Function Module (WE57) Client independent
    To link a message (ZINVRV) type to a function module (Z_IDOC_INPUT_ZINVRV) follow these steps:
    •     Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)
    •     Select an entry (EG. IDOC_INPUT_ORDERS) and copy
    •     Type in module name Z_IDOC_INPUT_ZINVRV
    •     Type in basic IDoc type as ZINVRV01
    •     Type in message type as ZINVRV
    •     Type object type as IDOCINVOIC (Invoice document) - Used for workflow
    •     Direction should be set to 2 for inbound
    •     Enter and save
    3.2.2.     Define FM settings (BD51) Client independent
    •     Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)
    •     Click on New entries
    •     Type in the name of the new function module Z_IDOC_INPUT_ZINVRV
    •     Enter 0 for mass processing in the output column
    •     Save and Exit
    3.2.3.     Maintain process codes (WE42) Client dependent
    A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.
    To maintain the process code follow these steps:
    •     Log on to the appropriate receiving system client
    •     Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)
    •     Choose Inbound with ALE service
    •     Choose Processing with function module
    •     Click on Processing with function module and choose create icon
    •     Click on New Entries
    •     Type in process code ZINR and give it a description and save
    •     Now you are asked to Please maintain codes added in ALE entry methods, enter and choose Z_IDOC_INPUT_FIRVSL and copy it. You should choose a FM similar to your one.
    •     Enter your process code ZINR
    •     Enter your function module Z_IDOC_INPUT_ZINVRV
    NOTE: The next 6 steps are used in workflow error handling.
    •     Enter IDPKFIDCMT in object type
    •     Enter MASSINPUTFINISHED in End event
    •     Enter IDOCINVOIC in IDoc object type
    •     Enter INPUTERROROCCURREDFI in IDoc start event
    •     Enter INPUTFINISHEDFI in IDoc End event
    •     Enter IDOCINVOIC in Application object type
    You will need to determine the task associated with object IDOCINVOIC, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.
    To set up the workflow area please consult the Workflow config guide.
    3.3.     Create inbound partner profile
    For each message type you need to maintain the inbound partner profiles.
    3.3.1.     Maintain receiving system partner profile (WE20) Client dependent
    To maintain inbound partner profiles read the document ALE configuration procedure:
    •     Add the message type ZINVRV with process code ZINR.
    •     Enter the output mode (background, immediately) for inbound processing and NO message code.
    •     Enter the position S and choose the ALE administrator 50000085. This position will then receive all the technical ALE errors via workflow.
    3.4.     Test
    Once the inbound function module has been debugged the scenario should be ready to test in its entirety. If problems occur, read through the relevant areas of this document to check your configuration or code.</b>
      Foe EDI 810 Mapping Refer  <b>http://www.altova.com/videos.asp?type=0&video=edimapping</b>.
    Online demo you can see,
    Thanks
    Manju

  • Hi i upgrade from lion to mountain lion to day on my mini mac,Since the upgrade i am getting no sound through my HDMI cable which was working fine on lion Checked the midi audio settings and system preferences to out on HDMi nothing no sound whats so ever

    Hi i upgraded from lion to mountain lion to day on my mini mac,Since the upgrade i am no longer getting sound through my HDMI cable which was working fine on lion Checked the midi audio settings and system preferences to out on HDMi nothing no sound whats so ever.Any one any ideas?
    I use a samsung TV for my monitor via HDMI.Tried all the system Audi setting nothing .Head phone and internal speakers are fine.

    Similar issue; Audio was working fine on Lion, now not on Mountain Lion. Have a Macbook Pro early 2011 with AMD Radeon HD 6750M, connected by thunderbolt through a Lacie LBD to a mini-displayport to HDMI adapter (n.b. same problem when not going through the LBD) to a Pioneer VSX 521 AV receiver. For me when I go into audio Midi settings all the volume sliders for the displayport device are greyed out and at zero. But when I click 'configure speakers', it's able to send out the test signals to each speaker. Part of the problem could be that I'm not getting the option to put out 6channel sound, only 2 or 8 channel. Since my system is Dolby 5.1, and I only have 6 speakers, I would have expected the 6ch option to be available. But I imagine there's more to it than that. Elsewhere someone has suggested playing with Remote Interactive over HD on an Onkyo device; I'll see if there's something similar on the Pioneer that can be changed. Any other suggestions welcome.

  • R/3 to XI manually IDOC sending and problem:

    <u><b>R/3 to XI manually IDOC sending and problem:</b></u>
    I sent IDOC using we19 transaction from R/3 system. After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
    I check XI (sxmb_moni) but there is nomessage there.
    <b>Problem 1:</b> I don't want R/3 ask me UID and password for XI access
    <b>Problem 2:</b> I want to see message in XI (sxmb_moni)
    Thanks

    Hi Cemil,
    >>>>After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
    check the RFC destination from R3 to XI (SM59)
    you will find the right one from your port (We21)
    you can also check step by step procedures
    for IDOC - XI in my book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • LSMW - Report to get IDOC failures and its external reference number

    Hi All,
    I'm currently using LSMW for data migration in CRM, for Business Partner and transaction data.
    I need to generated a report which covers the idocs which have failed and the external identifier for which it has failed. Currently the IDOC reports that are available OOB provide the IDOC number and the reason for failure. It will be great if I can get the external identifier of the transaction as well.
    I searched for a report in SAP but could not find any which gives this functionality.
    Please advice.
    Thanks in advance.

    Hi,
    1.)If you want the ouput in the same report program which triggers the idoc, it is better to use the control record information.
    You will get IDoc Number from XEDIDC(check the below code) and you can store the idoc number into an internal table if more idoc is expecting to be triggered.
         call function 'MASTER_IDOC_DISTRIBUTE'
              exporting
                MASTER_IDOC_CONTROL        = EDIDC
              tables
                COMMUNICATION_IDOC_CONTROL = XEDIDC
                MASTER_IDOC_DATA           = XEDIDD
              exceptions
                others                     = 5.
       read table xedidc index 1.
      append xedidc-docno to it_docno.
    And finallly use this to display in the output.
    2.) if u want it in a seperate report, then select based on date, idoctype, messagetype
    Regards,
    Sajith

  • Colour management in PS and monitor calibration

    I've calibrated my monitors colours with an Eye One Display 2 colorimeter, and for photoshop i've assigned the monitors colour profile it has created to the work area (Edit > Assign Profile).
    But for photography i take photos with AdobeRGB colour profile setting on my camera... should i be using this colour profile instead when working on the photos in PS? They look a little washed out. I'm guessing i should keep using my calibrated monitors profile instead?
    And when saving photos a jpgs for the web, should i tick the "ICC Profile" box that lists my monitors colour profile when saving? Because i've noticed that now some browsers have started supporting ICC profiles. So in Firefox 4 BETA for instance, if i dont use the ICC Profile setting the colours look washed out on other monitors.
    (Note that the ICC Profile setting for jpg is only available in File > Save As... if i go to File > Save for Web & Devices it has Embed Color Profile which is basically the same thing).

    Beany3001 wrote:
    ... after doing this and testing the images on other monitors this does not happen, dont know why it does it on my monitors but as long as the colours are ok on other peoples monitors, and the closest to my displays i can get them, this seems to be the best option.... When opening any sRGB or AdobeRGB images in PS CS5 they always look washed out (like the saturation has been turned down), i can directly open a RAW image taken with my camera that uses AdobeRGB and it will still look washed out.
    This only now happens after calibrating my monitor. Before this i could view any sRGB or AdobeRGB and they would look fine, not washed out in any way. I dont know why this happens, but i've seen other people mention this about PS as well after calibrating there monitors with a colorimeter (not sure if it's just with wide gamut displays). Do you have any explanation for this?...
    This is not normal and indicates a bad monitor profile. I have a wide gamut monitor too and I had some problems before properly profiling my monitor, after that images look perfect - in fact way better than any sRGB monitors that I've seen. This is especially obvious with sRGB photos from digital cameras because the manufacturers create algorithms that save the captured images with colors using the ideal sRGB color space which can be more accurately displayed on a wider gamut monitor when it is working properly.
    Beany3001 wrote.
    ...I've calibrated my monitors colours with an Eye One Display 2 colorimeter
    I'm not an expert with using these devices and I can't tell what could be the reason for generating a wrong color profile - it could be the device itself or wrong settings or probing. When choosing a colorimeter, I searched a lot for feedback and found various links like this one saying that Eye One colorimeters are not very accurate yet with probing wide gamut monitors. But I also read a lot of comments saying that they are fine and some people claim they are better. However only the manufacturer of Spyder 3 claim officially on their web site that it is wide gamut capable, so I got that one and so far it's working fine.
    Beany3001 wrote:
    ... It's why i would have liked to use my monitors profile as it's the only way i can get colours looking properly saturated and not dull...
    As I said earlier, by working on an image with a monitor profile, you are in fact turning off the color management and if you don't like the results when the color management is on that indicates that the color management is not set properly and is so wrong that you are better off without it. I think you should start the troubleshooting with properly generating an accurate monitor profile. Unfortunately I'm not a big expert with that as I got my colorimeter only several months ago and also ColorEyes Display Pro which is a profiling software from a different company. I set the calibration and probing settings following the instructions from the tech support of the profiling software and since I liked the results, I never spent time to understand in depth all settings and options.
    Beany3001 wrote:.... 
    I've read multiple times that the AdobeRGB colour space can do more colours than sRGB? I thought that only when you save in a limited format like JPG that the amount of colours are the same....
    Wider gamut does not necessarily is more colors. When you see those charts plotting gamuts as different 3D volumes or 2D cross sections, this is not the number of colors but saturation. You can have millions of colors on a narrower gamut than, let's say 10 colors with a much wider gamut. Think of the numbers as steps between colors and the gamut as how intensive the saturation can go. The number of colors depends on the bit depth 8 bit, 16 bit integer, 16 bit float, 32 bit float. JPGs are limited to 8 bit but the limit is to the number of colors (shades) not gamut. Check this link - it has jpgs saved with different profiles of various color spaces (gamuts)

  • Issue with IDOC occurence and SeeBurger message mapping

    Hey Guys
    While developing a EDI 850 to IDOC scenario i came across this issue with pre-delivered Seeburger mapping(A_850_V4010_to_I_ORDERS05).
    I actually need to post multiple IDOC's to SAP system in the same message so i changed the IDOC occurence to unbounded and re-imported that as a .XSD file in Integration repository.
    Earlier the pre-delivered message mappings provided by SeeBurger(under SEEBURGER_HIGH-TECH, 1.7.1 of seeburger) was working fine for me since i was posting only 1 IDOC but now the mapping is failing as the IDOC occurence has changed(unbounded).
    Is there a way we can do some settings on SeeBurger server or Bic so that we can use the pre-delivered mapping for Multiple IDOC's as well?
    I just want to make sure before i start off with doing whole of the mapping manually.
    Thanx
    Aamir

    Thanx for the input guys
    @Deepthi.
    Doing whole of mapping manualy is definitely the last option but i m looking for ways to re-use the pre-delivered SeeBurger mapping.
    >>Seeburger Mapping is only just to convert XML to EDI and EDI to XML.
    Bic mapping designer does this,i m dealing with message mapping of XI(convert source to target) not Bic designer right now,and Bic does more than just XML to EDI and vice versa,it handles other industry standards too.
    @Jens
    >>The XI message mappings from Seeburger in the Industry solutions are mapping templates
    Yeah,but the mapping template i have deals with 850 to ORDERS05,when i change IDOC occurence and re-import it back in Integration repository,it doesn't stays as ORDERS05,it has to be changed to user defined message interface(in my case MI_ORDERS05) so i m unable to use 850 to ORDERS05 template.
    @Seshagiri
    >>Open the Seeburger SWCV From the IR--goto External Def---Select the right one and copy it and paste it in notepad.
    Changing the occurence is not an issue,i want to re-use the pre-delivered mapping in Integration repository,which is not working.
    Looks like i need to do it manually
    Thanx
    Aamir

Maybe you are looking for

  • I cannot update my apps due to an incorrect email address...my iTunes info is correct but why isn't it asking for that?

    I am trying to update my apps and add ones that I have already downloaded to Itunes onto my new iphone 5s, however, every time I try to update them a different email pops up and asks for a password...I have no way of changing this email...MY current

  • Safari won't play audio or video without stutters.

    Console shows sandboxd - deny file-read-data errors at /Library/ScriptingAdditions as well as the same folder in my user directory. The error repeats non-stop (even when Safari is idle), approximately 50 messages per minute. PlugInProcess numbers cha

  • ERROR:max no of 100 conversations exceeded

    Dear All, I m tring to comfigure SAP XI(2004sr2) in 2nd step of SLD system : Connect SLD TO SEN (if CEN Present). I m getting following error Element 'BAPI_SLD_SUPPLIER_CONFIG_SET':Connect to SAP gateway failed Connect_PM  TYPE=A ASHOST=XIDEV SYSNR=0

  • Database crashes when placed in Archivelog mode

    My production database continues to crash when I place it in Archivelog mode. This happen especially during the period most of the heavy jobs is running. On the other hand, I created a clone of this very same database on another server in Archivelog

  • G/L a/c report

    Hi !!!! Friends is there any standard report in SAP where we can get the detail of all assigned G/L a/cs against a PR's Regards