Options to create IDOC in IDOC Flatfile
Hi,
we have requirement to process a fixed length file and map that structure to a standard IDOC and that IDOC has to be written out as IDOC flat file.I just want to get different opinions to see whether there are any other options other than using ABAP mapping like mentioned in that standard How to Guide IDOC XML to IDOC Flatfile.
My scenario is Fixed length file ->XI->IDOC Flatfile-->SAP(through File port with RSEINB00 Report)
I know there is module available in PI7.1,but we are still in PI7.0 with SP18 and no plans to up grage yet.
In the file I get single header,multiple details and single trailer records and I have to create multiple IDOCs(that many number of Detail Records) from a single file.So,I think I need to use BPM first to convert multiple IDOC to single IDOC and then use the ABAP mapping to convert IDOC XML to IDOC Flatfile.like two steps.
so I am thinking to avoid BPM,ABAP mapping and to see different options to create an IDOC flat file and the receiving SAP system can read the IDOC flatfile using standard File port.Receiving SAP is is very low version(I think 3.0) which is not supporting IDOC adapter communication from XI.
please suggest different options to get IDOC Flatfile or even directly sending IDOC (with ALE connection) that has been created after the mapping from ffixed length flatfile to standard IDOC.
Thank you in adavance.
Babu
> In the file I get single header,multiple details and single trailer records and I have to create multiple IDOCs(that many number of Detail Records) from a single file.So,I think I need to use BPM first to convert multiple IDOC to single IDOC
Hi Babu,
When PI reads the file from source system, it will read all the data into Single XML file and in message mapping just do 1:N mapping to create multiple IDOCs from single XML. You dont have to use BPM for this requirement.
You wait for better solution from other for 2nd part of your requirement i.e IDOC-XML to IDOC Flat file conversion.
Have a great day.
Cheers,
Jag
Similar Messages
-
How to create a simple idoc in practice? can you provide an example?
how to create a simple idoc in practice? can you provide an example with full source code?
Try with the follwoing steps
Sending System(Outbound ALE Process)
Tcode SALE ³ for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ¡V Create Model View
Tcode BD82 ¡V Generate partner Profiles & Create Ports
Tcode BD64 ¡V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ³ for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ¡V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ¡V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 ¡V Send Material Data
Tcode WE05 ¡V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Thanks & regards
Sreenivas
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Take a look at this guide.
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
Create The Extension Segment
Transaction: WE31
The first step in extending an IDoc is to create the new segments that will go into that IDoc. There are some rules that you need to follow when creating the segments:
- The name of each segment type must start with Z1
- For each field in the segment you need to define a field name and a
data element.
- The data element for the segment structure must be of data type CHAR.
How to create new segments:
Run the segment maintenance transaction WE31.
Type your new segment name, and click on Create.
Define the fields of your segment:
Field name
Data Element for the field (from the ABAP dictionary).
Do not change the Export length!
Save the segment
Run Segment -->Check to check the segment for consistency.
Release the segment for transport. Select Edit -->Set Release. Note that the Release column now has a check mark.
Create the Extension IDoc Type
Transaction: WE30
After you create the segments to be added to the extension type, you can create the extension type itself. Execute transaction WE30, enter the extension name, select Extension type, and click Create. You now have three options:
Create new type: Does not refer to other extension types
Create copy: Copies info from an extension type that already exists
Create successor: Extends an extension type from a previous release
of R/3. You can only have one version of an extension type for
each release.
Enter the Basic IDoc type that this extension type will extend.
The screen now shows the structure of the IDoc type you used as
a reference.
Position the cursor on one of the segments and click Create. This will insert an extension segment as a child of the selected segment.
NOTE: A segment cannot appear more than once in an IDoc type! You must control the use of duplicate segments with the segment attributes (the next screen).
The segment attribute screen appears. Enter the information and save.
Extension segments should not be mandatory (for future upgrades), and will need to have minimum and maximum number of instances defined. This answers the question, for each instance of the parent segment, how many instances of the child segment may we have?
You can press the Segment Editor pushbutton to view or change the segment definition.
Create the new Message Type
You can only use an extension IDoc type by assigning it to a message type. You can create a new message type for this.
First the message type itself needs to be created.
Transaction: WE81
Create a new entry and save. Use SAP established customer naming conventions (good form is to start with a Z and retain the rest of the related SAP message type, so, for example, MATMAS becomes ZMATMAS).
After creating the message type, associate it with the corresponding Basic IDoc Type and Extension Type. This relationship is used when IDocs are sent to or received from a partner to determine what segments are valid and what the hierarchy for those segments is.
Transaction: WE82
Create a new entry and enter the Message type, Basic IDoc type, Extension type, and Release, and save your data. Note: the release assignment is not valid for prior SAP releases.
One message type can be associated with many basic IDoc types; however, you need a one-to-one relationship for distribution via ALE.
regards,
srinivas
*reward for useful answers*</b> -
Find status of a sales order created using EDI IDOC
Hello everyone,
I have IDOC created for incoming sales order using FM 'IDOC_INPUT_ORDERS'.
When a sales order is created manually iva VA01, it prevents the order from being saved when a specific error is hit unless user resolved it first. However, when the order is created via EDI IDOC, the error is hit and it cannot be created. In the sapmv45a program, i will to say that if it is an EDI IDoc transacion for the order, let it bypass the error and create the order.
Can anyone pls tell me how to check the status of a sales order being created using EDI IDOC ?
Sy-batch does not work.
Thank you in advance.
JoyceJoyce,
If you pay attention the code in FM it is exporting value of da_edi_sign to memory id "SD_EDI_ACTIVE" stored in constant "da_memory_id". ('CONSTANTS: da_memory_id(13) VALUE 'SD_EDI_ACTIVE'.)
In your program you have two you have two options.
1. Declare a constant as in the FM and use that as mentioned below:
CONSTANTS: da_memory_id(13) VALUE 'SD_EDI_ACTIVE'.
IMPORT v_memid FROM MEMORY ID da_memory_id.
2. Hardcode memory id as below:
IMPORT v_memid FROM MEMORY ID 'SD_EDI_ACTIVE'.
Hope this resolves your problem.
Gajendra -
Requesting all to help me how to create lsmw using idoc method
hi
thanx for ur answer
requesting every body in the forum to help me how to create lsmw using idoc method.
regards,
balajiHi Balaji,
LSMW using IDOC is similar to using flat file method. Here you are getting data from IDOC container and mapping data with Idoc segments insted of flatfile column.
Hope this is what you are looking for. If helpful then dont forget to reward me for that
Darshan -
Creating a custom IDoc inbound function module
I have created a custom idoc.I wanted to create a custom IDoc inbound function module, this Function module will provide to launch a BAPI .Tell me how to "create" inbound function module for the custom idoc ?
Goto any standard for the Paramtetres
*" 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
*" REFERENCE(DOCUMENT_NUMBER) LIKE VBAK-VBELN
*" TABLES
*" IDOC_CONTRL STRUCTURE EDIDC
*" IDOC_DATA STRUCTURE EDIDD
*" IDOC_STATUS STRUCTURE BDIDOCSTAT
*" RETURN_VARIABLES STRUCTURE BDWFRETVAR
*" SERIALIZATION_INFO STRUCTURE BDI_SER
*" EDI_TEXT STRUCTURE EDIORDTXT1 OPTIONAL
*" EDI_TEXT_LINES STRUCTURE EDIORDTXT2 OPTIONAL
Do the below configs.
1.Recognise the funcmod as Inbound -BD51
2.Register the Function module in WE57 .
3.we42 Process code .
4. WE20 -PARTNER Profile
I hope it resolves ur Query.
Rgds
Sree M -
Creating a custom idoc.
Hi,
Could you please explain to me the step-by-step procedure to create a custom idoc having SAP defined segments?
Regards.sandeep,
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
/thread/199996 [original link is broken]
Don't forget to reward if useful..... -
Step by step procedure to create an Outbound IDOC's
Hi,
Can anyone let me know the steps to create an outbound idoc.
Regards
ShivaHi!
IDOCs:
- IDOC is an Intermediate Document'. It is simply a data container used to exchange information
between any two processes that can understand the syntax and semantics of the data.
An IDOC is created as a result of executing an Outbound ALE or EDI process.
In an inbound ALE or EDI process, an IDOC serves as input to create an application document.
-When an IDOC is created in the system , an unique number(16 Digits) is assigned to it.
This number is unique with in the client.
- IDOCs are independent of the sending and receiving systems.
- IDOCs are independent of the direction of data exchange.
- In the IDOCs, data is stored in text format.
- IDOC will wait until the Remote System is Active.
*IDOC Definition Components
- Basic Idoc Type: Basic Idoc type defines the structure and format of the business document
that is to be exchanged between two systems. Basic Idoc type can refer to an SAP provided
basic IDOC type or a customer developed basic IDOC type.
- A basic IDOC type has the following characteristics:
Name : A basic Idoc type can be assigned upto a thirty character name.
List of permitted segments: The segments make up the IDOC structure.
Hierarchy of segments : The hierarchy of segments specifies the physical sequence and
any parent - child relationship in the segments.
Mandatory Vs Optional Segments : When used in the IDOC type, each segment has
an attribute that defines whether the segment is option or mandatory.
Minimum/Maximum range for each segment: It defines the maximum and minimum
number of timesa data record corresponding to a segment cn exist in an IDOC.
- Segments : A segment defines the format and structure of a data record.
Segments are reusable componets. A segment consists of various fields that represent data
in data record.
IDOC Run time components:
- A unique IDOC number 16 digits is allocated.
- One control record is attached to the IDOC.
- Segments translate into data records.
- Status records are attached.
- Sytax rules are checked.
IDOC Record Types:
1. Control Record : The control record contains all of the control information about an IDOC,
this information basically includes the IDOC number, sender and receiver information,
and information such as the message type it represents and the IDOC type.
- there is only one control record per IDOC.
- The stucture of the control record is the same for all the IDOCs and is defined by SAP.
- The structure of the control record is defined by the data dictionary structure EDI_DC40.
- The control record is stored in the EDIDC table.
2. Data Record : Data records contain the application data. A data record has two sections
Administrative Section and a Data section.
- The Administrative section cotain the segment name, client, IDOC number, segment number,
hierarchy level information.
- The Data section of a data record is a stram of 1000 bytes where the actual data resides.
- The data record is defined by the data dictionary structure EDI_DD40.
- Data records for IDOCs stored in the EDID4 table.
3. Status Record : Status records are attaced to an IDOC throughout the process as
the IDOC achieves different milestones or encounters an error. At every milestone a statu code,
date and time are assigned.
- Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for
inbound processes.
Message Type: Identifies what type of information transformed between logical systems or partners.
Message type is not a local object type , it is transportable.
Port : A Port defines the medium in which data is exchanged between the two systems in
the ALE process, IDocs are transferred via memory.
1. TRFC ports are used for ALE communicaion.
2. File Ports used by EDI
3. CPI-C ports used to communicate with R/2 systems.
4. Internet ports used to connect with Internet Applications.
5. ABAP-PI ports used to process data via the ABAP programming interface.
6. XML ports used to process files in XML format.
Partner Profiles:
A partner profile has three views, which maintain different parameters for the partner.
1. The General Parameters View : Values are stored in table EDPP1.
2. The Outbound Parameters view : Values are stored in table EDP13, except for the
Message control parameter , which are stored in table EDP12.
3. The Inbound Parameters View: Values are stored in table EDP21.
Transaction Codes :
WE31- Segment Creation
WE30 - IDOC structure
WE81 - Message type creation
WE82 - Link between Message type and IDOC type.
WE21 - Creation of POrt
WE20 - Partner Profile creation
WE19 - Test tool for IDOC Processing.
SALE - ALE (Application Linking and Enabling) settings
Go through the link for basics related to IDOCs:
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6cdd507d11d18ee90000e8366fc2/plain.htm
Check these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
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
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Check these out..
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
Reward Points if it is Useful.
Regards
Tamá -
Is it possible to create a custom IDOC status?
Is it possible to create a custom idoc status on table TEDS1?
I have looked through customising and cannot seem to find a way to create a new idoc status.
Has anybody done this?Hello Chester..
hope this link will be helpful,
Re: IDOC status
*********Please reward points ,if found useful -
Error while creating an outbound idoc using idoc type delvry02
hi,
i getting the following error while creating an outbound idoc(outbound shipping notification) using message type " DESADV" and IDOC TYPE " DELVRY02"
ERROR:
" SPECIFY EITHER ADDRESS NO OR ADDRESS HANDLE"
MESSAGE NO: AM053
Help would be appreciated.
regards
leoThe message is kind of self-explanatory. It seems that some address (delivery address ?) is required but is missing from the IDoc. If it's a syntax error, then the segment with error will appear in red in WE05 transaction.
It is also possible that you have filled some field that you should have left blank and now SAP is trying to find an address based on that field.
Check your IDoc contents. It's really hard to tell from the distance since the requirements and configuration could be very different in different systems. Sometimes the OSS note search by message ID and number is also helpful. -
** File to IDoc scenario - IDoc not created in target system
Hi friends,
We are doing File to IDoc scenario. We made required setting in both application as well as XI system. While test the scenario, the file is picked up and successfully processed in SXMB_MONI, but the inbound IDoc is not created in target system. What could be the problem?
We are using DEBMAS message type DEBMAS06 IDoc type. We checked the following.
1) SM59 - Connections are OK both application and XI system
2) IDX1 - In XI System, we have assigned SAP<R/3> port.
3) IDX2 - IDoc is imported.
4) In ID - Sender File - Business Service - Adapter-Specific Identifier - Logical System name is given.
5) In application system. - Partner Profile maintained correctly.
6) SM58 - There is no error.
So, what could be the reason ?
Kindly reply, friends,
Thanking you.
Kind Regards,
Jeg P.Hi,
Check all the steps ..
File to IDOC
Do these configurations in R/3 and in XI...
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.
Thanks,
Satya -
How to create a inbound IDOC from flat file in Application server
HI All
Our requirement is to create the Inbound idocs from a flat file from application server with in R/3
Could any body please let me know the steps required for this.
Thanks
Malli1. Read the file using OPEN DATASET and read and fill up the segment info and fill the EDIDC header data
and then call function
CALL FUNCTION 'INBOUND_IDOC_PROCESS'
TABLES
IDOC_CONTROL = i_edidc
IDOC_DATA = i_edid4.
a® -
Idoc to a flatfile and then email it as an attachment
Hello,
I know it is possible to convert an Idoc to an flatfile (not xml) when you use a file communication channel. This is done by content conversion. But in my case the flatfile has to be sent as an attachment in an email. Is there a way this can be done by something simular like content conversion (as in the file communication channel)?
Best Regards,
Erik van LisdonkHi,
>>>>simular like content conversion
yes this is possible you can do the content conversion
in the mail adapter
have a look at this doc:
https://websmp101.sap-ag.de/~sapdownload/011000358700001186732005E/HowToConveModuleJMS.pdf
it's the same for mail adapter
Regards,
michal -
How can create SEGMENTS and IDOC TYPE in BADI in ECC 6.0 version
Hi All,
Can any one help, how to create SEGMENTS and IDOC TYPE in BADI in ECC 6.0 version.This is my task.
Given BADI name was----VENDOR_ADD_DATA_BI .
ThanksAnil,
look at this thread ..may be this helps you.
Re: 824 IDOC and BADI/User Exit
sateesh. -
Work items creating for GoodsMovement IDOCS
Hi Friends,
We have IDOC to File and File to IDOC scenario, we are able to post GRN files into SAP successfully, but for some idocs , work items are creating for some line items where there is error . After analysis we have come to know that there is some error in article or price is missing.
what i would like to know is instead of creating idoc for some items success and some with work items ,can we restrict if there is error in any line item.
for example:
let us say if i have one GRN file with 10 line items.when i post this File into SAP .. It post 7 items as success and for 3 items it creates workitems.
1) Is there anyway i can restrict the entire idoc , instead of posting 7 items once and after re-processing 3 items in second one.?
2) how to avoid creating work items?
one more thing I have created a backgrounduser for PI while posting to SAP. Some articles are showing as article is locked by piuser.
can anyone suggest how to overcome this..
Regards,
SumanSuman
What is the Message type / IDOC type your are using? You should be able to create one single IDOC with multiple line items instead of one IDOC for each item, provided the header information for the material document is the same for all the line items. In most cases this is possible.
Check your mapping in XI and see if you can club all the items in one single IDOC. Doing so will also prevent the material locked issue. But, point to note with this design is that you will be penalizing good records in your file just because one line item was in error.
KK -
Create a matmas idoc based on PIR information
Hello friends,
can you please help me on the following points please :-) ?
I need to create matmas idocs and these idocs should be sent on a web portal identified on our SAP system as a logical system. The vendors will have access only to the materials they supply. For this reason, I need to send in the matmas the GLN code corresponding to the vendor for which we have created a purchase information record. This way, on the web portal the display of matmas information will be organised according to GLN codes.
Question :
how can we create the MATMAS idocs according to purchase information records? I mean how can I create matmas idocs selecting the materials supplied by specific vendors???
is there any standard way to do it on SAP? or has it got to be done a specific way. and if so, do you have any idea on how to do it?
Thanks in advance for your very precious help,
Kind regards,
Karennare you thinking about manual creation in BD10, or something automatic?
BD10 has the standard F4 material search help.
If you need to do it regular and manually, then you may consider creation of a new included search help where you can search based on info records.
Maybe you are looking for
-
Advice on best arrangement for home network
This is my first post so go easy on me....please?! I have moved into a new apartment and am trying to set my network is the best way, but am struggling slightly. I have a WRT150N and WRVS4400N (Don't ask why I have both) both of which are brand new,
-
Configuring the Synchronous scenario in XI
Hello everyone! I want to configure a "Synchronous" scenario wherein when XI sends a message to a Marketsite, it waits for a response, then send back the response to the SAP system. My question is this, would I need to configure a "sender adapter" in
-
Hi, I have an XML file, and a XSD, both on local file system. How can I use Xerces' DocumentBuilderFactory to validate it? My code: static String jl = "http://java.sun.com/xml/jaxp/properties/schemaLanguage"; static String ws = "file:c:\\schema.xsd";
-
Foreign key validation while creating master/detail record in document mode
I am creating master/detail records in the document mode. And I am generating the master primary key in the create() method of the master Entity Object. Now I valdate the foreign key in the detail Entity Object's validateEntity() method by doing a qu
-
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: start
Hi I am Migrating my app from weblogic 8.1 to 10.3 . I am trying to run the startWeblogic.sh file its failing with below error .Please suggest me am unable to resolve CLASSPATH=:/opt/bea/patch_wlw1030/profiles/default/sys_manifest_classpath/weblogic_