Steps for IDOC scenario

Hi all,
I am doing an File to IDOC scenario.I have done with all the mappings and configurations in IR and ID.Please can anyone let me know the configurations that are to be done in R/3 and SLD for the posting of IDOC.
Please can anyone explain this to me.
Awaiting for ur reply
Amit

Hi Amit,
the following is from a thread/blog I cant find anymore. So I copy and pasted it!
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
Regards Mario

Similar Messages

Reg:Steps in IDOC Scenario

Hi,
    I am very new to IDOC concept so can anyone tell me what is the use and why do we want to create,
1)RFC Destination
2)Port
3)Logical sysytem name
4)Partner Profile ,in IDOC Scenario and also let me know the steps that I have to implement while doing that scenario.
Thanks in advance
B.Lavanya

Hi,
This is complete step by step document for configuring the idoc to file scenario along with ALE Settings
To Configure the IDOC TO FILE SCENARIO,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1)   Create an RFC Destination to the Sending System in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a)   Select create new button
b)   Enter the port name as SAP+SID (The starting char should be SAP)
c)   Enter the destination client
d)   Enter the RFC Destination created in SAP R/3 towards other system
e)   Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
                    SETTINGS IN SAP R/3
     We need to do the following settings in R/3
     Logon to Sap R/3 System
1)   Create an RFC Destination to XI in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client user & Password details of Destination system
h)   Test the connection and remote logon.Both must be succesful
2)   Create communication Port for Idoc processing Using Transaction(We21)
a)   First Select Transactional RFC and then click create button
b)   Enter the destination port name as SAP+SID (The starting char should be SAP)
d)   Enter the RFC Destination created in SAP R/3 towards other system.
e)   Save
3)   Create Partner Profile with Outbound Parameters (WE20)
a)   Create New
b)   Create the Partner no. name as same the logical system name of the destination system
c)   Select Partner type LS
d)   Enter details for Type: US/USER, Agent, and Lang
     Then Save
e)   Select Partner no. and LS which were create above
f)   Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g)   Select Message type
h)   Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I)   save
4)   In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
     and then assign logical systems
b)   Double click on Define the logical systems
c)   Give data for your Logicaal System and Name
d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e)   Assign the logical system name to the client
5)   Create Customer Distribution model in the transaction code BD64
1)   Click on the Create modal View button and enter the short text, Technical name etc as shown below
2)   Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3)   Save the Distribution model
    Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
    It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
    Then, you will be intimated about the partners, port creation, and outbound parameters creation
4)   Distribute Customer Distribution Model
    In the menu item GO to Edit->Modal View-> Distribute to the destination client
    Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
             Step2:Repository
1)       From the Integration Builder page, select Integration Repository. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server
2)       Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
         From the list of Software Component Versions, Choose your own software component version .Click Import.
3)       On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this software component. A screen will appear .Switch to display mode. After doing this first add a namespace under Namespaces.
         Your NameSpace is urn : DSZVFGD
4)       Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
         After this specify the connection parameters to the R/3 system:
4.1)     System :SAPFOX
4.2)     Client :800
         Then Save it. The new namespace will be visible under software component version node in the left frame.
         Under the namespace node, you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
4.3)     Application server:172.25.5.7
4.4)     System number:00
4.5)     User name: DEVELOPER
4.6)     Password: Password of Sap R/3 system.
         Then click continue .You will find IDOC node. Click on this node and select the   Idoc which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the    Idoc will be available into XI as Message types. So no need to create any Idoc Structure. We need to create a structure for file only.
5).      Under your namespace in the left frame, expand the node Interface objects. You will find a node DATA TYPES
6)        Create new data types.
6.1)      Right click on Data types and select New.
           Your Data Type is :DT_FILE
          In the data type Editor ,Create a structure having Elements of type String , integer, Boolean , Float etc as per the requirement.
          Save the object.
6.2)      The Import function for XSD files enables you to upload message definitions from external sources. The object type External Definition is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from External Definition
          no need to create Data types. They are imported directly as Message types.
6.3)      To do so, In the left hand frame Under Interface objects Create a new object of type External Definition and give name to it.
          Select the following.
6.3.1)    Category: XSD.
6.3.2)    Messages: From All Available Global Elements.
6.3.3)    File:
          Once the XSD is imported, click on Message tab , You should be able to see 2 messages(Request and Response)
7).      Create a new Message Type.
7.1)     In the left hand frame under Interface objects, right click on the Message types and select new.
7.2)     Give a suitable name to the Message type.(MT_ messagetype).
7.3)     For the section Data type used you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
         Save it.
8).     Create a Message interface
8.1)    In the left hand frame under Interface objects, right click on the Message Interface and select new and name(MI_ messageinterface) it
8.2).   The interface Should be Inbound and mode should be Asynchronous .It should reference your Message type(Use F4 or Search help).
        Save it.
9) .    Create a graphical mapping between the target document and the sender .
9.1)    In the left hand frame ,expand Mapping objects. Right click on Message mapping and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
9.2)    As Source message select your own Idoc .You can choose Search for Integration Object.As a reminder you can find your Idoc or Rfc under Software Component- >     Namespace->Imported Objects.
9.3)    As Target Message you can choose your Message type .Choose Search for Integration Object.
9.4)    Now that we have defined the Source and Target message, we can start defining the Mapping rules.
9.5)    Map the fields of Source document to the equivalent fields in Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the   Source fields to the respective Target Fields.
        Save It.
9.6)    You can also Test your Mapping by selecting the 'Test Tab'.
9.7)    Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
10).     Create an Interface Mapping.
10.1)   In the left hand Frame expand Mapping objects. Right Click on Interface Mapping and Name it. You are in a Interface Mapping Editor .Assign the following References.
10.2)   Source interface : Your Outbound Interface (The Source document(Idoc) interface).You can Choose Search for Integration Object.
10.3)   Target interface:    Your Inbound Interface( The Target document interface).
        Then Select 'Read Interface' and Assign your 'Mapping Program' .
        Mapping Program: Your Message mapping.
        Then Save it.
11.)    Finally , in the left hand frame ,go to your change list and Activate it
           STEP 3: Directory
1)      From the Integration Builder page, select Integration Directory. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server.
        Create a Scenario Object
2).     The First Step is to create a Scenario Object
        This will serve as container for all your configuration work. Create and save a scenario object
3)      In the left hand frame you can see the created scenario object. Under that Object Expand the node Service without Party and right click on Business System->Assign Business System
4)      In the wizard , leave the party name blank and then select your own Business System. Uncheck the box Create Communication Channel Automatically.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
5) .    Create a Communication Channel.
6).     Expand your service and right click on Communication Channel. Name your Communication Channel
        Here we need to configure the adapter.
     Since The Sender is IDOC , then there is no need of Sender communication channel and Sender Agreement.
          For the Receiver, Specify the following Parameters
6.1       For the adapter type , use the F4 help and select FILE.
6.2       Specify Receiver since the adapter will be sending XML files from XI to the FTP server.
6.3       Specify the following parameters.
          Transport Protocol: File Transport Protocol.(FTP)
          Message Protocol: File Content Conversion(since the xml file produce by XI need to be converted to text file)
          Adapter Engine: Integration Server
          For the File system access Parameters, enter the following
          Source Directory:VILAS
          File Name: Input.txt
6.4       For the FTP Connection Parameters, Specify the Following
          Server: 172.25.7.116
          Port: 21(by default)
          Data Connection: Passive
          Connection security: None
          Connection Mode: Permanently
          Transfer Mode: Binary
6.5       For Processing Parameters, Specify the following
          File construction mode: Add Time Stamp
          File Type: Binary
6.6       For Content Conversion Parameters, Specify the Following
          RecordSet Structure:
          Adapter Status: Active
          The receiver file adapter is now configured. Save your Communication Channel.
           Create an Receiver Determination.
7).       From the left frame Create a new Receiver Determination object. This is the main part of routing process, where you assign a receiver for your message.
7.1)      Select your sender service and interface.
          Sender:
          Party: blank
          Service: Sender service(Business system)
          Interface : Sender interface
7.2)      In the Configured Receivers area , choose the Service for the Target System.. Save your Receiver Determination
            Create an Interface Determination.
7.3)       Next create an Interface Determination object. Now that we have defined a receiver of message ,we need to assign an Inbound interface and an Interface mapping
7.3.1)     In the Receiver Determination   you just created, have a look at the area Configuration Overview for Receiver Determination   at bottom of your screen and press Refresh for that the Business system you assigned is displayed in that area as well.
7.3.2)     In the column Receiver(Partner/Service) open the details by clicking the node .The Entry Not defined shows you that there is no interface determination present.
           Right click on the Entry Not defined and select New specific, in order to create a new interface determination object
7.3.3)     You are now in the screen Edit Interface Determination. In the section Configured Inbound Interfaces select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
           After choosing the Inbound Interface, It is shown in the Interface Determination
7.3.4)     A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
7.3.5)     When you are done , Save the Interface determination object.
8.)         Create a Sender Agreement.
           In the left hand frame , right click on Sender Agreement ->New
8.1)       Specify the following:
           Party: blank
           Service: Select your own Business system
           Interface: Outbound Interface
8.2)       In the screen Edit Service Agreement use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
9.)         Create a Receiver Agreement.
           Finally you will create a 'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
9.1)       Go back to the main screen for your receiver determination. In the area Configuration Overview for Receiver Determination at the bottom of your screen click Refresh.
9.2)       In the Column Receiver Agreement(Communication Channel) right click and select New Specific.
           Specify the following:
           Party: blank
           Service: Select your own Business system
           Interface: Inbound Interface
9.3)       In the screen Edit Receiver Agreement for the field Receiver Communication Channel use the input help F4 and select your communication channel. Save and Close it
           Your Configuration is complete. Activate the objects.
PLZ REWARDS POINTS
VIKAS

Communication Channels for IDOC scenario

Hi!
I have a conceptual question regarding the communication channels within IDoc scenario.
Case 1:
- File_to_RFC scenario
Here I defined a File communication channel from business system A.
1a) For which system (business system A or B) do I need to define a IDoc communication channel?
1b) What is the RFC destination and Port I need here?
Case 2:
- IDOC_to_IDOC scenario
2a) Do I need in this scenario only one communication channel for business system A?
2b) What is the RFC destination and Port I need here?
Thank you very much!
Thom

>
Thom Heinemann wrote:
> Hi!
>
> I have a conceptual question regarding the communication channels within IDoc scenario.
>
> Case 1:
> - File_to_RFC scenario
> Here I defined a File communication channel from business system A.
> 1a) For which system (business system A or B) do I need to define a IDoc communication channel?
> 1b) What is the RFC destination and Port I need here?
>
in this case no IDoc CC is involved. All you need is a File sender adapter and RFC receiver adapter
> Case 2:
> - IDOC_to_IDOC scenario
> 2a) Do I need in this scenario only one communication channel for business system A?
> 2b) What is the RFC destination and Port I need here?
>
>
> Thank you very much!
>
> Thom
in this case you will need a IDoc receiver adapter only.
The basic settings:
In XI
SM59 - R3 connection pointing to R3
IDX1 - define the port with the above dest.
In R3
SM59 - R3 connection pointing to XI
WE21 - define the port with the above dest.
WE20 - Partner profile type outbound/Inbound
Further ref:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&

Receiver Determination steps for BPM scenario

Hi Experts,
Scenario : SOAP -> Calling different webservices
1. SOAP Client Request
2. Call the Initial webserive to get the unique Id. No need to pass any request to call this webservice, but it will give the response.
3. Take the Initial websrevice's response as a request to second webservice
4. Pass the SOAP client request to Third webservice
BPM steps
1. Receive Step for SOAP Request
2. Send Step for the Initial webservice call.
3. Transformation step Initial webservice response to request change.
4. Send Step for Second webservice (Pass the the Transformation step's target interface as a request)
5. Send Step for Third webservice ( Pass SOAP client request)
I am done with the BPM flow. Could you please help to do the Receiver Determination steps.
Usually I follow the below steps.
1. Sender Service to BPM
2. BPM to other services. I have a doubt with the second step. I am not passing the SOAP client request to Initial webservice. So, please tell me how to proceed further for the BPM Receiver Determination steps..
Thanks & Regards
Sara

Hey,
First, what is th purpose of your SOAP client request.
Is it just to trigger the BPM.
Second on what basis are you fetching the unique Id from initial web service.
If it is a normal scenario then, the reciever determination will be like this.
Soap client-> BPM
BPM->initial webservice
BPM->second webservice
BPM->third webservice
but in this particular scenario i dont know which data is being used to fetch the unique Id.
regards,
Milan

Business system name important for IDoc scenario message routing?

Hello all,
I have following problem.
I have to setup with our client an IDoc scenario which is a little difficult.
The client sends project IDocs from Client ERP system to his own XI system next to our XI sytem and at last Internal Order IDocs to our ERP system. We use for each environments (DEV, TEST, PROD) a separately SLD, the client a central SLD. In each environments we use the same business name for our XI system "BS_XI". Now the problem. The client aren't able to configure two times the same business name "BS_XI" for routing to our TEST respective Production environment. DEV will not used. I know the B2B scenario should be used in this case but i have no chance to think about this. Manager decision!
So what can be the workaround.
I think about to provide our client a different Business system name "BS_XI_PROD" with different technical system informations for our PROD environment. So for my understanding, the business system name is unimportant in this case, important here the technical informations which you are able to see in "Display Adapter-Specific Identifiers". Technical system, Port and RFC configuration.
The namings convention for Business system is unimportant in this case, yes?
Many thanks in advance!
Regards,
Jochen

Dear Jochen,
Can you please clarify a bit? Is it a problem between customer's XI system and your XI system?
I think you can use Parties here. In the Party you can define some additional identifiers, with which you can differentiate the incoming IDocs.
(e.g.: in the identifiers tab, Agency=BS_XI, Scheme=ALE#KU (defined in the customer's partner profile), Name=a defined name in the IDoc control record)
So with this you will have a "Business System+Party" as an identifier, where you can use several parties with the same business system.
I hope it helps!
Regards,
Andras

Need Message Type Creation Steps for Different Scenarios

Hi Friends,
I have done following steps for Outbound IDoc [Extended IDoc]
1. Create custom Message Type                           WE81
2. Create custom Segments               WE31
3. Create IDoc Extension               WE30
4. Create IDoc Type [Basic+Extu2019n]          WE30
5. Link Custom IDoc with Message Type          WE82
6. Activate CP for Custom Message Type                     BD50
7. Activate Change Pointers globally Flag on     BD61
8. Maintain custom message type in CDM                     BD64
9. Define partner profile for custom msgtype                    WE20
After completion of the above steps.
I am unable to do the following steps.
10. Checking the IDoc Creation                          BD10
          or
11. Execute CP IDoc generation Program     RBDMIDOC
Here these steps I am unable to find Message Type.
If we create message type thru BD53 [std idoc] it will come.
but my situation is for extended IDoc I need to create message type.
If any one worked on this situation Help me out.
Regards,
Mutyapu4u.
Edited by: naveen mutyapu on Jun 24, 2008 2:51 PM

Hi,
Check the link below:
http://www.****************/Tutorials/ALE/ALEMainPage.htm
Hope this helps..
Regards,
Sharath

Steps for idoc generation

HI all,
The requirement in my project is,
in tcode me21-create purchase order, if i enter data and click on save button, the corresponding idoc has to be generated. for this, the idoc is orders05. but after clicking save button how this idoc gets generated.
means, if i check in we05, idoc is to be displayed.
this all to be done in ECC5.0 server.
what are the configuration steps i need to follow?
plz help me.
rgds,
anil.

Hi Satish,
Go thru this thread-
SAP R3 ->Legacy system including master data using XI
<i>what are the configuration steps i need to follow?</i>
>>>There is already design is in place. For this there design/Repository objects are delivered by SAP.
SO you need to just configure the scenario in the directory. Like Idoc-XI->Target System scenario.
Regards,
Moorthy

Steps for Idoc to EDI Subsystem

Hi all,
Can anyone tell me the steps that i have to worry about to send an idoc immediately to EDI Subsystem
I mean what all things i have to specify while creating ports and partner profiles etc
Thanks

Sending Order Confirmations by EDI (SD-SLS)
Use
By setting up and using the Electronic Data Interchange functions in the R/3 System, you eliminate the need to print documents and send them through the standard mail system. Instead, you send the information electronically. This method is more practical, convenient, and allows you and your customer to process data faster.
In this EDI scenario, you process and send order confirmations to a customer's R/3 Purchasing system.
Prerequisites
Application
Customizing
To process outbound order confirmations, you need to make all of the necessary EDI settings in Customizing for Basis. You make settings for output control in Customizing for Sales and Distribution.
Output Control
The standard SD condition components are:
Condition component     Value
Sales document type     AA
Output determination procedure     V10000
Condition type     BA00
Transmission medium     6 (EDI)
Access sequence     0001
Processing subroutine     Program RSNASTED, form routine EDI_PROCESSING
Partner function     SP (sold-to party)
Application     V1
Condition records for outbound order confirmations are maintained in Customizing for Sales and Distribution. Choose Basic Functions  Output Control  Output Determination  Output Determination Using the Condition Technique  Maintain Output Determination for Sales Documents.
IDoc Interface
Define the EDI partner profile for your partner (transaction WE20) by entering the following data for the outbound parameters for partner profiles and the additional profiles for message control:
Field     Value
Message type     ORDRSP
Partner type     KU (customer)
Partner function     SP (sold-to party)
Receiver port     e.g. SUBSYSTEM
Output mode     e.g. Transfer IDoc immediately
Basic type     ORDERS04
Process code     SD10
Activities
Create an order. When you save the document, the system uses your settings in output control to find the appropriate condition record and send confirmation of the order by EDI. To review and maintain output data in the document, choose Extras  Output  Header.
Receiving Acknowledgments via EDI (MM-PUR-GF-CON)
Use
You have arranged with your vendor that that latter is to send you acknowledgments in respect of purchase orders or outline agreements received from your company. (Note: both kinds of acknowledgment are generally referred to as "order acknowledgments" in the system. The corresponding EDIFACT term is "order response" (ORDRSP).)
You have the option of working exclusively with acknowledgments. The acknowledgment is then purely informative in nature, since only the acknowledgment number is recorded in the system.
If you wish to receive different kinds of vendor confirmation, such as both order acknowledgments and shipping notifications (also known as advance shipping notices - ASNs), it is possible for quantities and dates to be entered in the system automatically).
For more information on this topic, refer to the MM Purchasing documentation ( Confirmations from the Purchasing Viewpoint and Receiving Confirmations via EDI).
Prerequisites
Application
To work with several categories of vendor confirmation, you must:
u2022     Enter a confirmation control key on the item detail screen
u2022     Set up the confirmation control facility in Customizing for Purchasing (Purchasing  Confirmations  Set up Confirmation Control). There you can specify the order in which you expect confirmations from your vendors, for example.
Under Confirmation sequence, you can:
u2022     Specify tolerances for date and price checks
u2022     Allow vendor material changes (VMat indicator)
u2022     Adopt vendor price changes (Price indicator)
Do not use a confirmation control key if you work exclusively with acknowledgments.
IDoc Interface
You have made the following settings for your EDI vendors in Customizing for Purchasing (Purchasing  Messages  EDI  Set up Partner Profile):
Parameters for Inbound Messages
Field     Value
Partner type     LI
Partner role     LF
Message category     ORDRSP
Process code     ORDR
Processing     Initiate immediately or process via background program
Activities
When an acknowledgment is received in the form of an incoming EDI message, the system checks whether a confirmation control key has been entered in the relevant PO or outline purchase agreement.
u2022     If there is no confirmation control key, only the acknowledgment number is entered on the item detail screen.
u2022     If there is a confirmation control key, the system updates the confirmation overview. That is to say, the dates and quantities set out in the acknowledgment that has just been received are recorded and taken into account in the overview. To view acknowledgments that have been received, choose Item  Confirmations  Overview from the item overview. Column C (creation indicator) contains the value 3, meaning that the acknowledgment was received via EDI. The system also enters the IDoc number in the External document column.
An IDoc can always acknowledge one purchase order only. The acknowledgment relates to the PO item, not to any individual schedule lines.
Exceptions
When an acknowledgment is received via EDI, the system automatically checks quantities, prices, and dates. In checking quantities, it applies the over- and underdelivery tolerances set for the item. You can set tolerances for prices and delivery dates in Customizing for Purchasing under Set up Confirmation Control.
The tolerances you define apply to all vendors. Using the enhancement MM06E001 provided by SAP, you can specify that the tolerances do not apply to certain vendors.
If the acknowledged quantities, prices, and dates vary from those set out in the PO or purchase agreement, the system issues a warning message. In this case, the purchasing document is not updated.
For more information on this topic, refer to the section Error Correction (Receiving Confirmations via EDI) of the MM Purchasing documentation.
Sending PO Change Notices via EDI (MM-PUR-PO)
Use
This section describes how to transmit a change notice relating to a purchase order that has already been sent to a vendor.
The function corresponds to the transmission of a purchase order via EDI.
Prerequisites
Application
You have already successfully transmitted the original purchase order to the vendor via EDI.
Message Control
You have created message condition records for your EDI vendors (Purchasing  Master data  Messages  Purchase order  Create).
Use the message type NEU to transmit PO change notices.
IDoc Interface
You have made the following settings for your EDI vendors in Customizing for Purchasing (Purchasing  Messages  Set up Partner Profile):
Parameters for Outbound Messages
Field     Value
Application     EF ( Purchasing: purchase order)
Message category     ORDCHG
IDoc type     ORDERS02 or ORDERS04
Process code     ME 11 (ORDCHG: PO change notice)
If you wish to transmit PO conditions or texts to your vendor, you must create an IDoc view. For more information on this topic, see Sending a Purchase Order via EDI.
Activities
Change an existing purchase order via Purchasing  Purchase order  Change. Make the necessary changes and save the PO.
The new message is compared with the last successfully transmitted message. PO change notices indicate whether any new items have been added to the PO, and/or whether any already transmitted items have been changed.
When the message is transmitted, only those changes that are simultaneously new and print-relevant are included. The system sets the change indicator for the new message. To check the change indicator, choose Header  Messages in the PO item overview.
See also:
MM Purchasing: Creating a Purchase Order
Cross-Application Components: Customizing Message Control in Purchasing (MM): Example: Purchase Order
Receiving Order Changes by EDI (SD-SLS)
Use
In this EDI scenario, you receive and process order changes sent by a customer from an R/3 Purchasing system.
Prerequisites
Application
General
You can receive and process order changes in your system only on the basis of an existing order.
Customizing
To process incoming order changes, you need to make all of the necessary settings in Customizing for Basis. There are no special settings for Sales and Distribution.
IDoc Interface
Define the EDI partner profile for your partner (transaction WE20) by entering the following data in the header and detail screen for inbound parameters:
Parameter     Value
Partner type     KU (customer); if the IDoc is sent from an R/3 system via tRFC (in a typical case with ALE scenarios), enter LS for logical system!
Message type     ORDCHG
Process code     ORDC
Processing     Process immediately
Allowed Agents     Enter an R/3 user or an organizational unit, for example.
Activities
Inbound Processing
The IDoc interface receives the IDoc and reviews its control record. According to this record and the corresponding partner profile, the IDoc is transferred to the function module IDOC_INPUT_ORDCHG in Sales and Distribution. The ALE services are called.
The system processes the IDoc in the background, using the data records in the IDoc to determine the relevant order.
If processing is successful, the system updates the sales order. The IDoc is sent back to the IDoc interface which updates the status records in the IDoc.
Exception Handling
If it cannot determine an order, or if an error occurs in processing, the system determines the relevant agent(s) and sends a workitem to the integrated inbox(es). An agent can pick up the workitem to process the IDoc or simply end processing.
To display an IDoc for order changes, choose Environment  Display facsimiles in the order. The system displays a dialog box of object links where you can choose Linked IDocs.

What are exercise steps for RTI scenario

hi,
we have configured AII and EM using RTI scenario configuration guide.
To run the scenario in a systmatic way, is there any any instruction booklet containing steps and the transactions. like go to this system and do this, go to that system and do that.
regards,
thanks in advance,
Sathyanag

hi,
The configuration Guide available for RTI processing in AII 4.0 should have enough information to help you out.
regards,
arul sekar.

Steps for IDOC trasnfer from APO to R/3

Hi,
I know we can transfer the of data say PR from APO to R/3 is done via CIF.
Suppose if I need to transfer the same PR via IDOC instead of CIF how can I do it? Let me know the steps to follow and way to find out how the data got transferred (CIF or IDOC)?
Thanks for your reply.
Best Regards,
SIva.

Did you check log in SLG1 , /SAPAPO/C3 . whats is the message in the log.
Can you check your queues SMQ1/SMQ2 in both the system , is there any block ?

Inbound Queues getting stuck up in PI7.1 for Idoc scenario Mpackg. enabled

Hi Experts,
We have an issue while processing Single Idocs in PI 7.1.
we have extended MATMAS05 and we are processing these via PI to FTP folder.
The inbound queues are frequently getting stuck.we will be sending atleast 1000 idocs every hour from R3.The processing time is very slow for this interface and its impacting other interfaces which we are currenlty having.
We have followed the webblog by William Li "Step-by-Step Guide in Processing High-Volume Messages Using PI 7.1's Message Packaging" but still the processing time for Single Idocs is very slow.
We have to use single idocs as we will send only the changed materials from R3.
Could you please assist us in overcoming this issue.
Many thanks in advance.
Points will be awarded for valuable feedback.
Cheers
Jyoti

Hi Jyoti,
Message Packaging works PI7.0 SP 13 and PI7.1 .
we have to configure Message Packaging manually ,
Step 1) 1. Enable packaging for the integration server
SXMB_ADM -> Change Configuration (F9), create a new entry:
Category: RUNTIME (PI7.1)
Parameters: PACKAGING Current Value: 1 (for active) .
Default Value in PI7.0
Current Value: 0 (for inactive)
Step 2) Create "Package Configuration Type u201C
Use Transaction SXMS_BCM .
Configuration Type : Any name.
Description: any text to describe the configuration type .
Wait Time : 60 seconds
Number: 100
Maximum Package Size. 2 MB
Step 3) Create "Sender/Receiver Definition
Transaction :   SXMSIF (Create New Entry).
Sender/Receiver ID:PACKAGE_DEMO .
Description :
Interface Name: Interface Name used in Receiver Determination.
Interface Namespace:   Interface Namespace used in the Receiver Determination .
Step 4: Create "Specific Package Configuration"
Transaction :    SXMS_BCONF .
Step 5: Package Monitoring
TX: XMSPKSTATCNF
Follow above steps and configire message packaging , then you feel diference,
actuualy i configured message mackaging,i am feeling the difference.
if any issues let me know.
Cheers,
Raj

Authorization problem for idoc scenario

HI,
Can some one tell me what are the authorizations required to post a custom idoc to R/3 from XI ? I have done a scenario like file->IDOC(custom).When i execute the scenario it is successful in MONI. When i execute the transaction IDX5 in XI, i am seeing the status as No authorization to send IDocs with message type ZMASEMPDETAILSMT....Any help on this will be appreciated.
Regards,
Sudheer.

Hi,
Please check SAP/ERP
WE20 navigate to logical system and check the INPUTPARAMETER (ZMASEMPDETAILSMT must be a value there)
ON XI check WE21 (define a port to your ERP)
On XI create CC IDOC receiver and point to this port
Helpful Link:
https://websmp202.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700003604082004E
Daniel

IDOC Scenario Steps

I want to master IDOC scenario...
Where i can see step by step of IDOC scenario?.
I want steps in ECC side and steps involved in XI side....
Never saw a nice blog showing each step in details like wiki pages....
Can somebody write or do we have a detailed blog?.

HI,
See the below links
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm - Collection of IDoc to Single File
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
File-XI-IDoc Scenario - File to Idoc
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
see the below links to get more details about IDocs
ALE/ IDOC/ XML
Troubleshooting of ALE Process - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
Please check this online document for ALE and IDoc.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
serialization /people/alessandro.guarneri/blog/2006/11/26/content-based-serialization-dynamic-queue-name-in-xi
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.henrikfrank.dk/abapexamples/IDOC/gl_postings2.htm
http://searchsap.techtarget.com/ sDefinition/0,,sid21_gci852485,00.html - 45k - Cached - Similar pages
Process codes in IDOC
http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b806743d711d1893e0000e8323c4f/frameset.htm
http://edi.stylusstudio.com/msg04418.htm
Check this link to find out the difference b/w ALE,IDOC and BAPI
http://www.sap-img.com/abap/ale-bapi.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
---Split messages :
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
/people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
Regards
Chilla

Doubt regarding ALE SETTINGS in IDOC scenario.

Hi Friends,
        I have some doubts regarding ALE settings for IDOC scenarios, can anyone please clarify my doubts.
For exmaple take IDOC to FILE scenario
The knowledge i got from SDN is --
One need to do at the R3 side is --- RFC DESTINATION (SM59) for the XI system.
                                                   --- TRFC PORT for sending IDOC to the XI system
                                                   --- CREATING LOGICAL SYSTEM
                                                   --- CREATING PARTNER PROFILE
               at the XI side is --- RFC Destination ( For SAP sender system)
                                       --- CREATING PORT for receiving IDOC from the SAP sending system(IDX1).
1. Do we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself or in XI system or in both systems we create these logical systems? Is this a mandatory step in doing ALE configurations?
In IDOC to IDOC scenario-------
2. Do we craete two RFC destinations in XI system? One RFC DESTINATION for the Sender R3 system and another RFC DESTINATION for the Receiver R3 System? and do we create RFC DESTINATION for the XI system in receiver R3 system? If not.....y we don't create like this........Please give me some clarity on this.............
3. If we use IDOC adapter ,since IDOC adapter resides on the ABAP STACK ,we don't need sender communication channel ,for the similar reason----
y we r creating receiver communication channel in the case of FILE to IDOC scenario?
4. Can any one please provide me the ALE settings for IDOC to FILE scenario,
                                                                                FILE to IDOC scenario,
IDOC to IDOC scenario individually.
Thanks in advance.
Regards,
Ramana.

hi,
1. Yes, we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself and
it is a mandatory step in doing ALE configurations
2. We create 1 RFC destination each in R3 and XI.
    R3 RFC destination points to Xi and
    XI RFC destination points to R3
3 We need to create Communication Channel for Idoc receiver as the receiver channel is always required but sender may not be necessary
4. ALE settings for all IDOC scenarios are same as follows....
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
Reward points if helpful
Prashant

Regarding idoc to idoc scenario

Hi Masters,
can u provide step by step blog or doing idoc to idoc scenario.....
and second thing is tht working on production server.. i had done all the design part as wel as the config part for sending the same idoc to the reciever system .. it is bcoz later two fields are added to that sender idoc so i did all the mappings related to that .. after completing all when i checked the xml the two fields it is not showing in the xml.. wht might be the error can u explain me ...
its very urgent ... waiting for u r reply .
thanks in advance,
jp..

Hi Jp k
refer these links for ur scenario
for idocs scenario have a look to this how to guide:
https://websmp203.sap-ag.de/~sapdownload/011000358700003604082004E/HowTo_IDOC_XI_Scenarios.pdf
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
Scenario - IDoc - XI - RFC - IDoc
Thanks !!

Steps for IDOC scenario

Similar Messages

Maybe you are looking for