Steps of idoc
what is the steps of idoc
Hi check these links
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
<b>PLEASE CLOSE ALL UR PREVIOUS THREAD BY ASSIGNING POINTS TO USEFUL ANSWERS</b>
Regards
- Gopi
Similar Messages
-
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.LavanyaHi,
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 -
hello i need to migrate lsmw using idocs ?can anybody please tell me the ateps in idoc method
Regards
priyaHi,
If you have knowledge of IDoc you can easily perform the following steps for LSMW through Inbound Idoc
To use IDoc inbound processing, you must first perform the following steps:
Step 1.Define or select a file port for transporting the file. Optionally, you can also create a tRFC port.
Step 2. The partner type has to be defined or selected.
( WE20 to Maintain Partner Profiles )
For example-
Partner type:US
Report name:/SAPDMC/SAP_LSMW_PARTNERTYPES
Form routine:READ_USER
Short text: Testing
Step 3. The partner number has to be defined or selected.
For example
Partner number:LSMW
Partner type:US
Partner status:A (active)
Type:US
Language: EN or DE
ID:Your user ID
Step 4. IDoc inbound processing must be activated, and the workflow customizing must be checked. Both of these tasks are performed once in each system.
For this Step 4you need to doi the following things
I) Choose Workflow customizing.
The Workflow Customizing screen appears.
II)Choose Perform Automatic Workflow Customizing.
The auto customizing log for the runtime system is displayed.
III)Check the entries.
The following entries of the workflow runtime system must have a green checkmark assigned to them:
Maintain System Administrator for Workflow.
Configure RFC Destination.
Classify Decision Task as General.
Activate Send to Objects
Thanks
PK -
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 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 ? -
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
ThanksSending 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. -
Step by step custom IDOC creation
Hi,
Can someone give me step by step to create a custom IDOC completely from scratch along with its real tim scenarion ?hi Tushar,
check it out
There are basically two types of IDOCs.
Basic IDOCs
Extended IDOCs
Idoc Components
Basic Idoc
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extension Idoc
Extending the functionality by adding more segments to existing Basic IDOCs.
Creation of IDoc
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.
Create IDOC Type
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
u can also check all these links related to idocs
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sap-img.com/
http://www.sappoint.com/abap.html
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
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://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
Regards,
Naveen -
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
AmitHi 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 -
IDOC send step not running with exception in BPM?
Hello,
hope this is a simple question, but we are running with a problem here which is not answered well in SAP help or sdn. Possibly I didn´t find the right blog.
Situation:
We created a BPM with a send step (IDOC receiver) in a block (after a receive step starting the BPM) (That´s simple so far!).
The send step (async IDOC) in the block is connected in its attributes in field "system error" to an exception branch defined in the same block.
In this except.branch the process should send back to sender system a message via RFC and the last step in this exception branch is to interrupt the proces.
But now we tried to do a test. In this test we modified the receiver address of the send step (IDOC reciver) so that the receiver could not be reached, which results in a system error in SXMB_MONI (Service unavailable).
But this doesn´t work. The BPM starts the send step to the unavailable receiver, SXMB_MONI shows a system error step, but then the BPM continues with the next step after the block without starting the exception branch.
Any idea why the exception branch is not called?
Best regards
DirkHello again,
we are one step further now.
We did the same with an RFC instead of the IDOC send step.
Same result:
The service is not reachable. So the step results in an system error.
But as we could see in the monitoring SXMB_MONI the block with the exception and this send step (RFC) is passed before the step gives back this error!
So it looks like connection problems do not trigger an exception?
Any help is welcome!
Best regards
Dirk -
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 -
Can anybody send ALE/IDOC sample steps fot MATMAS?
Hi friends,
Can anybody send ALE/IDOC sample steps fot MATMAS?Steps for IDOC.
Communication Settings will take care by basis.
Communication settings.
1. BD 54 Create Logical system. (To get logical system FM
OWN_LOGICAL_SYSTEM_GET)
2. SCC4 Assign logical system to client
3. SM 59 Create RFC Destination.
4. WE 21 Create port.
Partner setting.
5. WE 20 Create Outbound partner profile.
(Creating outbound partner profile message type with MATMAS and IDOC type with MATMAS01-05 )
6. BD 64 Create Distribution model. (It will act as a BAG to carry the list of receiver details for all message type.)
7. Run BD10 for outbound and BD11 for Inbound. -
Hi All,
Can any one please give me the step by step ale-idoc toturial.about the steps to send data from one client to other.
Regards,
buntyHi,
<b>
It gives, entire idoc documentation.
http://help.sap.com/saphelp_nw04/helpdata/en/3b/beb13b00ae793be10000000a11402f/frameset.htm
To develop a new custom ALE scenario, comprises 5 steps:
1. Design and develop the custom IDoc with its 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 providers system.
Figure 2: Example Purchasing & Selling scenario
We will develop a custom IDoc to carry the billing number from the Service Receivers system to the Service Providers 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 well 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 segments 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.
IDOC Programming
Index
Process Steps for IDOC Programming 3
Interpreting An IDoc Segment Info 3
IDoc Type The Structure of The IDoc File 5
Defining The Message Type 6
Define Valid Combination Of Message and IDoc Types 6
Process Steps for Inbound IDOC Programming 7
Characteristics of Inbound function module 7
Assigning a processing function 8
Processing Codes 9
Workflow Handling 12
Create Inbound Partner Profile 12
Sample Code Snippet 14
Execution Steps for inbound Idoc: 17
Testing of Inbound Idoc: 19
Process Steps for Outbound IDOC Programming 21
Common Steps 21
Create Outbound Partner Profile 21
Sample Code Snippet 23
Execution Steps: 26
Testing of Outbound Idoc: 26
Change Pointers & Reduction of IDOCs. 26
What is IDOC
IDocs are SAPs file format to exchange data with a foreign system. IDocs is the acronym for Intermediate Document. This indicates a set of (electronic) information, which builds a logical entity. An IDoc is e.g. all the data of a single customer in your customer master data file. Or the Idoc is all the data of a single invoice.
IDocs are an ASCII file format to exchange data between computers; the format is chosen arbitrarily
IDocs are similar to segmented files; they are not a description language like ANSI X.12, EDIFACT or XML
The IDoc contents are processed by function modules, which can be assigned in customizing
Process Steps for IDOC Programming
The following steps are required for inbound and outbound IDOC Programming.
Interpreting An IDoc Segment Info
All IDoc data records are exchanged in a fixed format, regardless of the segment type. The segments true structure is stored in R/3s repository as a DDIC structure of the same name.
Go to transaction code WE31. Enter the name of the Segment, which is to be created (fig 2.1).
E.g. Create the segment ZEMPMASTSEG
Fig 2.1 WE31- IDOC Segment main screen.
Fig 2.2 WE31 IDOC Segment definition screen.
In the above screen user can enter the fields, which are necessary for the segment. Once all the necessary fields will be populated then Save the transaction. After Saving release the version of the Segment by selecting the version and through menu Edit -> Set release.
Same way create one or more segment.
Fig 2.3 WE31 IDOC Segment definition screen for another segment (ZEMPMASTHEADERSEG).
IDoc Type The Structure of the IDoc File
The IDoc type is the name of the data structure used to describe the file format of a specific IDoc.
An IDoc is a segmented data file. It has typically several segments. The segments are usually structured into fields, however different segments use different fields.
The IDoc type is defined with transaction WE30, the respective segments are defined with transaction WE31 as per the point 2
Go to transaction code WE30. Enter the IDOC Type name.
Fig 3.1 WE30 IDOC Type main screen.
Add the segments to the IDOC Type as per the requirement.
For e.g. in the fig 3.2 it shown that IDOC Type is having only one segment ZEMPMASTHEADERSEG, which is having one child segment ZEMPMASTSEG
Fig 3.2 WE30 IDOC Type segment screen
For each segment developer (double click on the segment) can set the minimum, maximum number of segment in a sequence.
Fig 3.3 fig 3.4
Defining the Message Type
The message type defines the context under which an IDoc is transferred to its destination. It allows using the same IDoc file format to use for several different applications.
The message type together with the IDoc type determines the processing function.
The message type defined using transaction code WE81.
fig 4.1 WE81 Message Types
Define Valid Combination Of Message and IDoc Types
The valid combinations of message type and IDoc type are stored in table EDIMSG, using transaction WE82.
The declaration of valid combinations is done to allow validation, if the system can handle a certain combination.
Fig 5.1 WE82 Message Type Assignment
Process Step for Inbound IDOC Programming
Characteristics of Inbound function module
Before assigning the function module to Inbound process code, its characteristics must be set with the transaction BD51. This step is mandatory before assigning the function module to Inbound process code.
For inbound processing you need to tell, whether the function will be capable of dialog processing. This is meant for those functions, which process the inbound data via call transaction. Those functions can be replayed in visible batch input mode to check why the processing might have failed.
Fig 6.1
Here the main characteristic is Input Type. It means How are IDoc packages processed? and having values like
Input Type Short Text
0 Mass Processing
1 Individual input
2 Individual input with IDOC locked in CALL TRANSACTION
Also another property Dialog Allowed can be set here. With Dialog allowed IDocs can be processed in dialog mode.
Fig 6.2 BD51 Characteristics of Inbound Function Module
Assigning a processing function
The combination of message type and IDoc type determine the processing algorithm. This is usually a function module with a well-defined interface or a SAP business object and is set up in table EDIFCT.
The entry made the points to a function module, which will be called when the IDoc is to be processed. The entries for message code and message function are usually left blank. They can be used to derive sub types of messages together with the partner profile used.
Used transaction code WE57 for assigning function module to IDOC Type.
Fig 7.1 WE57 Assign Function Module to Message and IDOC Type
Fig 7.2 Assign a handler function to a message/message type
Process Codes
R/3 uses the method of logical process codes to detach the Idoc processing and the processing function module. They assign a logical name to function instead of specifying the physical function name.
The combination message type/IDoc will determine the logical processing code, which itself points to a function. If the function changes, only the definition of the processing codes will be changed and the new function will be immediately effective for all IDocs associated with the process code.
For inbound processing codes you have to specify the method to use for the determination of the inbound function.
The Inbound processing code can be attach to the function module using transaction code WE42
Fig 8.1 WE42 Define Inbound Process Code
You need to tick, if your function can be used via the ALE engine. This is the option you would usually choose. It allows processing via the ALE scenarios. See fig below
Fig 8.2 WE42 Set properties of Inbound Process Code
See fig 8.4
Fig 8.3 WE42 Set the Message type for the Inbound Process Code
Fig 8.4 WE42 Fill the details of the Inbound Process Code.
The properties set in the above fig 8.4 are used for the workflow handling when the IDOC is having any error.
Properties, which are useful in the workflow processing, are as follows.
Object Type It is a business object created using transaction code SWO1 and used as a handler
Starting Event - Will triggered the workflow on occur of Error.
Ending Event - Will terminate the workflow after processing the
Workflow Handling
Refer: - Workflow Guide
Create Inbound Partner Profile
For each message type you need to maintain the inbound partner profiles. Maintain receiving system partner profile using WE20 (See fig. 10.3). Add the message type in the Senders inbound parameter.
Following steps will be followed for creation of partner profile (Inbound).
Add the message type (e.g. ZEMPMSG) into the inbound parameter by clicking .
Fig. 10.1 WE20 Addition of message type in Inbound Partner Profile
On the next screen enter the message type , process code. In the Processing by function module block select the radio button based on the need. If you clicked on Triggered by background program then the IDOC will be collected and will triggered by another program which will run in background and if the second option Triggered immediately is clicked then the IDOC will be processed by the function module as soon as it is triggered.
Fig. 10.2 WE20 Inbound Parameters.
Fig 10.3 WE20 Create Partner profile
Sample Code Snippet
Important Steps are as follows.
1) Unpacking of IDOC: - Unpack the IDOC into the respective segments.
2) Process Data: - Process the unpacked data.
3) Error Handling.
4) Workflow triggering.
FUNCTION Z_IDOC_INPUT_EMPMAST.
""Local interface:
* IMPORTING
*" REFERENCE (INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*" REFERENCE (MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
* EXPORTING
*" REFERENCE (WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*" REFERENCE (APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*" REFERENCE (IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*" REFERENCE (CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
* TABLES
*" IDOC_CONTRL STRUCTURE EDIDC
*" IDOC_DATA STRUCTURE EDIDD
*" IDOC_STATUS STRUCTURE BDIDOCSTAT
*" RETURN_VARIABLES STRUCTURE BDWFRETVAR
*" SERIALIZATION_INFO STRUCTURE BDI_SER
* EXCEPTIONS
*" WRONG_FUNCTION_CALLED
DATA: S_EMPMAST LIKE ZEMPMASTHEADERSEG.
DATA: T_EMPMAST LIKE ZEMPMASTSEG OCCURS 0 WITH HEADER LINE.
DATA: WA_EMPMAST LIKE ZEMPMAST.
DATA: L_FLAG VALUE 'Y'.
CLEAR S_EMPMAST.
REFRESH T_EMPMAST.
check if the function is called correctly *
IF IDOC_CONTRL-MESTYP <> 'ZEMPMSG'.
RAISE WRONG_FUNCTION_CALLED.
ENDIF.
WORKFLOW_RESULT = 0.
Unpacking the IDoc
LOOP AT IDOC_DATA.
CASE IDOC_DATA-SEGNAM.
WHEN 'ZEMPMASTHEADERSEG'.
MOVE IDOC_DATA-SDATA TO S_EMPMAST.
WHEN 'ZEMPMASTSEG'.
MOVE IDOC_DATA-SDATA TO T_EMPMAST.
APPEND T_EMPMAST.
ENDCASE.
ENDLOOP.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-MSGV1 = IDOC_CONTRL-IDOCTP.
IDOC_STATUS-MSGID = '00'.
IDOC_STATUS-MSGNO = '398'.
Processing Data
LOOP AT T_EMPMAST.
MOVE-CORRESPONDING T_EMPMAST TO WA_EMPMAST.
INSERT INTO ZEMPMAST VALUES WA_EMPMAST.
G_OKCODE = SY-SUBRC.
IF G_OKCODE <> 0.
L_FLAG = 'N'.
Error Handling
IDOC_STATUS-STATUS = '51'.
IDOC_STATUS-MSGTY = 'E'.
IDOC_STATUS-MSGV2 = 'Employee & already exists'.
REPLACE '&' WITH WA_EMPMAST-EMPNO INTO IDOC_STATUS-MSGV2.
IDOC_STATUS-SEGNUM = SY-TABIX + 1.
APPEND IDOC_STATUS.
ENDIF.
AT LAST.
ENDAT.
ENDLOOP.
IF L_FLAG <> 'Y'.
Workflow Triggering
CLEAR RETURN_VARIABLES.
RETURN_VARIABLES-WF_PARAM = 'Error_IDOCs'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
WORKFLOW_RESULT = '99999'.
ROLLBACK WORK.
ELSE.
IDOC_STATUS-STATUS = '53'.
IDOC_STATUS-MSGTY = 'S'.
IDOC_STATUS-MSGV2 = 'Employee Info inserted'.
APPEND IDOC_STATUS.
ENDIF.
ENDFUNCTION.
Execution Steps for inbound Idoc:
To execute inbound idoc go to Transaction we19 give the Idoc number execute the transaction
It displays a screen with control, data, and status records. Click Standard inbound OR inbound function module buttons and process the idoc.
i) Standard inbound:
If you have selected the standard inbound button it displays a screen with the standard setup:
II) Inbound function module:
If you select the in bound function module button displays the below screen you can enter the function module name which you want to execute
If you select Check box Call in debug mode you can execute the function module in debug mode.
Call transaction Processing:
In Background:
The function module is called in the background
This setting is only important if the function module to be called reacts accordingly to the importing parameter 'INPUT_METHOD'. This is therefore only valid for function modules which implement the application functionality using the command 'CALL TRANSACTION'.
In foreground :
The function module is called in the foreground.
This setting is only important if the function module to be called reacts accordingly to the importing parameter 'INPUT_METHOD'. This is therefore only true for function modules which implement application functionality using the command 'CALL TRANSACTION'.
In foreground After error:
The function module is called in a background session. This becomes a session in the foreground after the first error has occurred.
This setting is only important if the function module to be called reacts accordingly to the importing parameter 'INPUT_METHOD'. This is therefore only true for function modules which implement application functionality using the command 'CALL TRANSACTION'.
Now it will post the idoc.
Testing of Inbound Idoc:
If you need to check the status of idoc Go to Transaction ZE05 give the idoc number in the idoc number select option execute the transaction.
Then displays a screen with Out box and Inbox . select the idoc number in the Inbox Shows the control record , data record ,status record .select the status record and check for the idoc status Then you will be known the idoc is successful posted or not.
The idoc which has been posted into SAP successfully will have the status 53.
The list of the other valid status for Inbound Idoc are as follows:
Status Message Description
50 IDoc added
51 Error: Application document not posted
52 Application document posted
62 IDoc passed to application
64 IDoc ready to be transferred to application
74 IDoc was created by test transaction
Process Steps for Outbound IDOC Programming
The following steps are required for Outbound IDOC Programming.
Common Steps
The steps for new segment creation, new Idoc Type, new Message Type and linking between message type and Idoc Type are same as Inbound Idoc Programming. The detail Steps for such activities are mentioned in the Page 2 to Page 5.
Create Outbound Partner Profile
Use Transaction WE20 and select the Receiver Partner. Then add message type ZEMPMSG in the outbound parameters. The partner profile needs to be created at the ReceiverLogical System(LS)/Customer(KU)/Vendor(LI)/Bank(B)/Benefits provider(BP)/ User(US) only.
Then double click on the Message type ZEMPMSG and it navigates to the following screen where user has to set the following attributes:
Receiver port as A000000001 for RFC
Packet Size field as 1
Idoc type Z_EMPMAT_IN in basic type field
Set the Syntax check box
Set the output mode as Transfer Idoc immediately
Save the changes.
Coding Steps:
1) Create an Executable Program Based on specification.
2) All the Important Data should be displayed as Parameters with mandatory.
i) Message type
ii) Sender port
iii) Sender partner
iv) Sender partner function
v) Receiver port
vi) Receiver partner
vii) Receiver partner function
3) Select the data based on selection screen into an internal table.
4) Read the selected internal table and fill the Header segment.
5) Now Loop the internal table to fill other Segments.
6) Fill the Control segment data.
7) Call the proper Function module and pass the data to the function module
To create the idoc.
8) Change the status of idoc based on the function module return code.
9) If FM return code is 0 set status to 03.
10) See the demo program Z_IDOC_OUTBOUND_EMP for more Clarification.
Sample Code Snippet
REPORT Z_IDOC_OUTBOUND_EMP .
TABLES: ZEMPMAST.
DATA: F_IDOC_CONTRL LIKE EDIDC,
T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
T_IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE.
Data: Begin of t_zempmast occurs 0.
include structure zempmast.
Data: end of t_zempmast.
data:wa_ZEMPMAST like ZEMPMAST.
data:wa_ZEMPMASTSEG like ZEMPMASTSEG.
Data: wa_ZEMPMASTHEADERSEG like ZEMPMASTHEADERSEG.
CONSTANTS: C_BASIC_IDOC_TYPE LIKE EDIDC-IDOCTP VALUE 'Z_EMPMAT_IN',
C_Z1CLIPS_SEG_NAME LIKE EDIDD-SEGNAM VALUE 'Z1CLIPS',
TRUE VALUE 'X',
FALSE VALUE SPACE.
Selection Screen----
SELECTION-SCREEN BEGIN OF BLOCK EMP WITH FRAME TITLE TEXT-001.
SELECT-OPTIONS : S_EMPNO FOR ZEMPMAST-EMPNO.
SELECTION-SCREEN END OF BLOCK EMP.
PARAMETERS: P_MESTYP LIKE EDIDC-MESTYP
DEFAULT 'ZEMPMSG'
OBLIGATORY.
PARAMETERS: P_SNDPRT LIKE EDIDC-SNDPRT,
P_SNDPRN LIKE EDIDC-SNDPRN,
P_SNDPFC LIKE EDIDC-SNDPFC.
PARAMETERS: P_RCVPRT LIKE EDIDC-RCVPRT,
P_RCVPRN LIKE EDIDC-RCVPRN,
P_RCVPFC LIKE EDIDC-RCVPFC.
Selection of data
Perform select_data.
Create Idoc
perform creat_idoc.
CLEAR F_IDOC_CONTRL.
*& Form select_data
text
--> p1 text
<-- p2 text
FORM select_data.
Selecting the required data based on Selection Screen
select * into corresponding fields of table t_ZEMPMAST from ZEMPMAST
where EMPNO in s_EMPNO.
ENDFORM. " select_data
*& Form creat_idoc
text
--> p1 text
<-- p2 text
FORM creat_idoc.
Creating Header Segment
if not t_zempmast[] is initial.
T_IDOC_DATA-SEGNAM = 'ZEMPMASTHEADERSEG'.
Populating Idoc data table with header Segment
perform prepare_segment using wa_zempmast.
T_IDOC_DATA-SDATA = wa_ZEMPMASTHEADERSEG.
APPEND T_IDOC_DATA.
Creating other Segments.
loop at t_zempmast into wa_zempmast.
CLEAR T_IDOC_DATA.
Filling item segment
T_IDOC_DATA-SEGNAM = 'ZEMPMASTSEG'.
perform prepare_segment1 using wa_zempmast.
T_IDOC_DATA-SDATA = wa_ZEMPMASTSEG.
Adding the item segments into idoc table
APPEND T_IDOC_DATA.
CLEAR T_IDOC_DATA.
endloop.
Filling Control data.
F_IDOC_CONTRL-MESTYP = P_MESTYP.
F_IDOC_CONTRL-IDOCTP = C_BASIC_IDOC_TYPE.
F_IDOC_CONTRL-SNDPRT = P_SNDPRT.
F_IDOC_CONTRL-SNDPRN = P_SNDPRN.
F_IDOC_CONTRL-SNDPFC = P_SNDPFC.
F_IDOC_CONTRL-RCVPRT = P_RCVPRT.
F_IDOC_CONTRL-RCVPRN = P_RCVPRN.
F_IDOC_CONTRL-RCVPFC = P_RCVPFC.
Creating idoc
PERFORM DISTRIBUTE_THE_IDOC TABLES T_IDOC_DATA
T_COMM_CONTROL
USING F_IDOC_CONTRL.
endif.
ENDFORM. " creat_idoc
*& Form prepare_segment
text
-->P_T_ZEMPMAST text
FORM prepare_segment USING P_T_ZEMPMAST like ZEMPMAST.
Filling header Segment
wa_ZEMPMASTHEADERSEG-REPNAME = sy-repid.
wa_ZEMPMASTHEADERSEG-DATE = sy-datum.
wa_ZEMPMASTHEADERSEG-TIME = sy-uzeit.
ENDFORM. " prepare_segment
*& Form prepare_segment1
text
-->P_WA_ZEMPMAST text
FORM prepare_segment1 USING P_T_ZEMPMAST like ZEMPMAST.
filling item segment
wa_ZEMPMASTSEG-EMPNO = P_T_ZEMPMAST-EMPNO.
wa_ZEMPMASTSEG-EMPNAME = P_T_ZEMPMAST-EMPNAME.
ENDFORM. " prepare_segment1
*& Form DISTRIBUTE_THE_IDOC
text
-->P_T_IDOC_DATA text
-->P_T_COMM_CONTROL text
-->P_F_IDOC_CONTRL text
FORM DISTRIBUTE_THE_IDOC TABLES T_IDOC_DATA STRUCTURE EDIDD
T_COMM_CONTROL STRUCTURE EDIDC
USING F_IDOC_CONTRL STRUCTURE EDIDC.
READ TABLE T_IDOC_DATA INDEX 1.
IF SY-SUBRC = 0.
insert and distribute the idoc
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
EXPORTING
MASTER_IDOC_CONTROL = F_IDOC_CONTRL
TABLES
COMMUNICATION_IDOC_CONTRO -
Steps to migrate lsmw using Idocs
hello i need to migrate lsmw using idocs ?can anybody please tell me the ateps in idoc method
It's very urgent , help plz.
Thanks in Advance
jdkumargoto--> lsmw.
settings--->idoc inbound processing
here enter file port, trfc port, partner name.
then follow below steps(as suggested above by a frnd)
Project : 060_BUS_TRANS
Subproject : SERVICE_TICKET
Object : SRV_TICKET_ZSVT
click on the execute button .you will reach the screen :
The screen shows the 15 steps to Run the lsmw
Step 2) select the first step ( Maintain object attributes) and click the execute button.After clicking on the execute button you will reach at. the screen
Here you have to specify ( Message type and basic type)
click on the BACK button
Step 3) select the 2nd step ( Maintain source structures) and click the execute button
Here you have to specify the source structures.
Step 4) Select the 3rd step ( Maintain source fields) and click on the execute button :
Here you have to specify the fields present in the source structure
Step 5) select the 4th step ( Maintain structure relationship ) and click on the execute button :
Here you have to specify relationship between source and target structures
Step 6) select the 5th step ( Maintain field mapping ) and click on the exécute button :
Here you have to map the fields between source and target structure. Also you have to apply conversion rules here if any
STEP 7) select the 6th step and click on the exécute button
Here you can define any fixed value or user define routines
Step 8) select the 7th step ( Specify files) and click on the exécute button :
At This screen we have to specify the files for This we should be in change mode .So please click on the button shown in the above screen. After clicking on This button you will be in change mode and will be able to specify the files :
Step 9) select the 8th step ( Assign files) and click on the exécute button
For assigning files yoy should be in change mode do the same thing click on the button as shown in the above screen :
Then assign the files to different structures.
Step 10 ) select the 9th step ( Read Data) and click on the exécute button :
After clicking on the exécute button you will reach to the screen
Again click on the exécute button . After clicking on the exécute button you will reach to the next screen
Here you will see data is read.
Step 11) select the 10th step ( Display read data) and click on the exécute button :
Here you can see your test data present in test files assign to source sturcture
Step 12 ) select the 11th step ( Convert data) and click on the exécute button :
After clicking on the exécute button you will reach to the screen
Click on the exécute button as shown on the : After click on the exécute button you will reach to the next screen
Data is converted
Step 12th ( Display converted data is same as Display read data )
Step 13 ) select the 13th step ( Start idoc generation) and click on the exécute
button :
At this step Idoc is generated using converted data
Step 14) select the 14th step ( Start idoc processing ) and click on the exécute button :
After clicking on the exécute button you will reach to the screen :
And then click on the exécute button : After clicking on the exécute button you will reach to the final processive screen
If data is processed correctly you will see ( 53 Status message with green sign -
Creation of SO from PO through Idocs in Same client
Hi frnds,
Can we create SO from PO through IDOC's in the same client with different company codes.
Ex: PO created in 100 client in company code AB00. i have to create SO in 100 client in company code AB01.
Any suggestion on this is highly appreciated. Please provide the steps and idocs or let me know the other approach.for posting the IDOC to same system
use this logic
The steps to send and receive an IDoc in the same system are as follows:
u2022 Create a Dummy Logical System.
Goto T-Code SALE-> sending and Receiving Systems -> Logical Systems -> New entries. Enter SYSID_CLNT, but this one is Dummy so use the first two characters of the SYSID and prefix 'D' then underscore and then the Client number.
E.g., If ERP_100 is the logical system of the R/3, then create ERD_100 as the dummy system.
u2022 Create Port for the Original System, (ERP_100)
Goto WE21 and select Transactional Port and press the Create button. Name the Port as "SAP" concatenated with the SYSID in our example it would be SAPERP Select the appropriate version and enter the RFC destination of the system that you are working on in this case it will be 'ERP'.
u2022 Create Partner Profile in partner type LS:
Receiver Side (Outbound to): In Partner type LS name ERD_100create the Outbound Parameters, give the Message type, Receiver Port same as the port we created in step 2. Enter the Basic type.
Sender Side (Inbound from): In partner type LS name ERP_100 create the Inbound Parameters, give the appropriate message type and the process code.
u2022 Now create the stand alone program to send the IDoc:
The program will at some point calls the MASTER_IDOC_DISTRIBUTE function module. When you pass the EDIDC structure it will be populated as follows:
i_edidc-mestyp = message type.
i_edidc-idoctp = basic type.
i_edidc-rcvprt = 'LS'.
CONCATENATE 'SAP' sy-sysid INTO l_port.
i_edidc-RCVPOR = l_port.
i_edidc-rcvprn = 'ERD_000'.
CONCATENATE sy-sysid '_' sy-mandt INTO l_sndprn.
i_edidc-SNDPRN = l_sndprn.
i_edidc-sndprt = 'LS'.
i_edidc-sndpor = l_port.
u2022 Observe that the Sender port and the receiver port is the same, this does the trick. The outbound Idoc is sent on the port SAPERP with the Sender as ERP_100 and receiver as ERD_100 and then the Inbound IDoc is also sent to the same port SAPERP with the Sender as ERP_100 and receiver as ERD_10.
this is the method for creating logical system and setting
and use the respective function module and mesg type for posting it.
cheers
s.janagar
Edited by: Janagar Sundaramoorthy Nadar on Apr 29, 2009 6:32 AM -
Unable to change the length of field in idoc segment
Dear all,
My requirement is to change the length of a field(Z field) in a segment (Z Segment). I tried the following but in vain
1)Tried to Cancel the release and then change the length of the domain. Unfortunately it is givin an error saying "Error while resetting release of segment ZC9DEMARA01".
I also tried cancelling hte release of extension and then cancelled the release of segment
2) Created a new version, but in new version the earlier fields are diabled. So I am unable to edit.
I have gone through some of the links available in SDN but I could not solve as I am unable to cancel the release in the first step.
[Idoc segment field length changes]
Could you please help me.
Thanks in advance!
regards,
AravindHello Aravind,
I Have created one Segment type with some fields, changed the field length also its working.
just try to cancel the release and change the length of the filed and do it set release again.
Try it .
Thanks,
santhosh
Maybe you are looking for
-
HI friends, Can any one help me out in creation of view i am suceeded in creation but while display it is showing no records i think i am going wrong in selection conditions....can anyone give me clear steps to create a view.?
-
I imported about 1000 photos on my macbook pro and when i look at my all images folder it shows duplicates of all pictures and i have over 6000 photos in the folder. What can be done to clear up hard drive space on my computer.
-
Safari with IIS: Too many connections?
Has anyone out there any experience using Safari with Microsoft's IIS? In particular, the 'Personal Edition' of IIS that only allows 10 concurrent connections? I'm finding that whenever I access one of the websites running on IIS using Safari, I can
-
Time Machine incomplete backup - how to recover files
I did not complete a Time Machine backup due to a failing hard drive. I can see from the space left on my external drive that Time Machine backed up a substantial number of files. Is there a way to go into the backup file to recover a few key file
-
TS1812 firmware file is not compatible
firmware file is not compattible