Help in fulfilling IDoc Matmas05

Hi everyone. I have a question, I hope someone could help me with this.
How can I find out the required fields and valid values to fulfill them in order to create a MATMAS05 Idoc in R/3?
I am currently integrating R/3 with XI and I getting the following error when I try run an Idoc with the values I mapped:
"No description transferred"
I would assume it refers to the column described as "description" in E1MAKTM (WE19). The strange thing is that this column is fulfilled.
Thank you very much.
Regards,
Tadeu

Dear all,
I solved the problem on my own, as a reference for those who face the same problem, the minimum required fields on my case where the following:
EN MATMAS05 / IDOC
Columna
EN EDI_DC40
TABNAM
DIRECT
IDOCTYP
MESTYP
SNDPOR
SNDPRT
SNDPRN
RCVPOR
RCVPRN
EN E1MARAM
@SEGMENT
MATNR
MTART
MBRSH
MATKL
MEINS
GEWEI
VOLUM
VOLEH
TRGAR
SPART
PRDHA
MHDRZ
MHDHB
EN E1MAKTM
@SEGMENT
MSGFN
SPRAS
MAKTX
SPRAS_ISO
Regards,
Tadeu.

Similar Messages

Flat file to idoc MATMAS05 - mapping

Hi,
I want to create 2 Idocs from one recordset.
Can any one tell me how do I map this Recordset to an Idoc?
Example source and target IDOC structures:
Source:-
 <Recordset>
 <SA010>
 <IDENTS>1234</IDENTS>
 <BEZ>Dummytxt</BEZ>
 </SA010>
 <SA088>
 <IDENTS>1234</IDENTS>
 <MARC1>010</ MARC1>
 <MARC2>020</MARC2>
 </SA088>
 </Recordset>
Target:-
 <MATMAS05>
 <IDOC BEGIN="1">
 <E1MARAM SEGMENT="1">
 <MATNR>1234</MATNR>
 <E1MARCM SEGMENT="2">
 <WERKS>010</WERKS>
 </E1MARCM>
 </E1MARAM>
 </IDOC>
 </MATMAS05>
 <MATMAS05>
 <IDOC BEGIN="1">
 <E1MARAM SEGMENT="1">
 <MATNR>1234</MATNR>
 <E1MARCM SEGMENT="2">
 <WERKS>020</WERKS>
 </E1MARCM>
 </E1MARAM>
 </IDOC>
 </MATMAS05>
Thanks and Regards,
Eren

Hello Varun,
My flat structure:
<Recordset>
<SA010>
<IDENTS>1234</IDENTS>
<BEZ>Dummytxt</BEZ>
</SA010>
<SA088>
<IDENTS>1234</IDENTS>
<MARC1>010<>
<MARC2>020</MARC2>
</SA088>
</Recordset>
The MATNR field is <IDENTS>. I can pick the value from node <SA010> or <SA088>.
Thanks

I need help to create idoc from scrach.

i need help to create idoc from scrach.

Swamy Katta,
Please read "[the rules|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement]" before you post any further, and confirm that you have read them?
=> Search first, ask questions later please!
Julius

Std idoc matmas05 details in SAP

Hi, How to see the details (logic etc) in R/3 System for standard idoc MATMAS05 to prepare a FS to interface with external system. Please advise what should i mention in FS in this regard. thank you.

for this IDoc, check all the Mandatory Fields & Mandatory Structures.
In your FS write the logic for Mandatory fields & structures & give it to Technical person for pick & fill data in Mandatory fields first.
At second step, check which optional fields you need to fill, give the logic for these fields also.

Plz help me ALE/IDOC Scinario documentation

hi and all,
plz help me ale/idoc scinarios documentation plz send to me.
thanking u one and all.

Hi
ALE:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Outbound:
Step 1. Application document is created when transaction is saved.
 2. Message control is invoked.
 3. Messages are processed by system.
 4. Messages are Edited (if desired).
 5. Output (ALE / EDI) is checked
 6. Validate against Message control record from Partner Profile
 7. Application Document is saved.
 8. Entry NAST table is created for every selected output program
 along with Medium & Timing.
 9. Check for Process Immediately .
 If (yes)
 Determine Processing Program from TNAPR Table.
 ELSE
 Execute RSNASTED Program.
 10. Read Partner Profile to determine Process Code.
 11. Process Code points to the Function Module & Invoked.
 12. IDoc is generated.
 13. Check for ALE Request.
 if (Yes)
 Perform Filters, Conversions, Version Changes etc.
 Else.
 IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
 2. Subsystem calls Functional Module EDI_DATA_INCOMING from
startRFC program.
 3. Data in Control Record is validate against the Partner Profile.
 4. IDoc is generated in Database and syntax check is carried out.
 5. IDoc file is deleted once file read.
 6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
 7. Check for Process Immediately.
 If NO
 Execute RBDAPP01 Program
 Else
 Read Process Code from Partner Profile
 Process Code Points to Function Module
 Application Document Posted.
IDOC
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
>>>> SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
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/
Reward points for useful Answers
Regards
Anji

Help me on idoc

Hi Abap Experts
I'm Bharadwaj, New to this fourm
can any one help me on idoc ....
how to create idoc ,how to test idoc ,how to post idoc ,how to test status of idoc.
is there any good links is there ....
if it is possible plz send me sample code for idoc.
Thnx in advance.
Cheers.
Bharadwaj

Hi bharadwaj,
welcome to sdn world.
below link might help you.
http://help.sap.com/saphelp_erp2004/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
check these also....
BC620 - SAP Idoc Interface Technology
BC621 - SAP Idoc Interface Development
reward wtih points for helpfull answers and close the thread if your question is solved.
regards,
venu.

IDoc MATMAS05 does not update MARA-AENAM

Dear colleagues,
I am using IDoc for maintenance of material master records. It's basic type is standard MATMAS05. When I trigger IDoc that needs to change material master record, this material master record is updated correctly, except AENAM field (Name of accounting clark who changed record). In my IDoc structure I have field which defines AENAM. This field is filled with proper information, but after IDoc running ERP MARA-AENAM is filled with logon user defined in RFC Destination settings and not with value from IDoc's AENAM.
Could you help me to solve this issue and have proper data in MARA-AENAM (from IDoc AENAM field)?
Regards,
Harry

the coding is undoubtedly taking the last change date and user from the SY structure:
IF neuflag = space
   and ( not rmmg2-new_inst is initial or
         not rmmg2-new_inst_v is initial or
         not rmmg2-new_inst_a is initial ).
    mara-laeda = sy-datum.
    IF user IS INITIAL.
      mara-aenam = sy-uname.
    ELSE.
      mara-aenam = user.
    ENDIF.
ENDIF.
And this sounds logical to me, as if this would not be the case, then you could change data with an IDOC and let it look as if this change was done by someone else.

File to IDOC(MATMAS05)

I'm trying simple scenario for File to MATMAS05 IDOC. I filled in the required fields it specified by Red in the message mapping, but still I get the following error when I try to test the mapping
Structure with min!=max without mapping
I dont understand what exactly this means..did anyone get this before? how to fix this error?
Thanks,
Kalpana

hi
Below one is for Cremas
u just follow the same procedure for u r Idoc with u r fields..
I think it is helpful for u upto some Extend...
2.11.4     Map the fields of the source document to the equivalent fields in the IDoc. This can be achieved easily by locating the target field in the IDoc structure and then drag-and-drop from the source field to target field. Please refer to the table below for the mapping rules (segments and fields are sorted according to their order of appearance in the IDoc).
Source field in Vendor     Target field in CREMAS03
VendorNumber     E1LFA1M à LIFNR
Address à Country     E1LFA1M à LAND1
LastName     E1LFA1M à NAME1
Address à City     E1LFA1M à ORT01
Address à Zip     E1LFA1M à PSTLZ
SearchTerm     E1LFA1M à SORTL
Address à Street     E1LFA1M à STRAS
VendorNumber     E1LFA1M à E1LFB1M à LIFNR
VendorNumber     E1LFA1M à E1LFM1M à LIFNR
Currency     E1LFA1M à E1LFM1M à WAERS
2.11.5     Now we have to assign constants to certain fields and attributes in the IDoc (for segment qualifiers, hardcoded values and XML attributes). This can be achieved by following the procedure below. Refer to the table below for more details on the mapping rules.
2.11.5.1     Double-click on the target field in the IDoc.
2.11.5.2     At the bottom of the screen, select Constants from the drop-down list for function type.
2.11.5.3     Click on the function Constant. Now the empty constant appears in the screen.
2.11.5.4     Double-click on the empty constant and assign a specific value.
2.11.5.5     Connect the constant to the target field.
Constant     Target field in CREMAS
1     CREMAS03 à IDOC à BEGIN
1     E1LFA1M à SEGMENT
009     E1LFA1M à MSGFN
COMPANY     E1LFA1M à ANRED
LIEF     E1LFA1M à KTOKK
1     E1LFA1M à E1LFB1M à SEGMENT
009     E1LFA1M à E1LFB1M à MSGFN
3000     E1LFA1M à E1LFB1M à BUKRS
31000     E1LFA1M à E1LFB1M à AKONT
A1     E1LFA1M à E1LFB1M à FDGRV
1     E1LFA1M à E1LFM1M à SEGMENT
009     E1LFA1M à E1LFM1M à MSGFN
3000     E1LFA1M à E1LFM1M à EKORG
2.11.6     For the segments E1LFB1M and E1LFM1M please assign an empty constant. This is necessary because these segments are optional in the IDoc. Although some underlying fields have already been mapped, If the parent node is not explicitely used as the target of a mapping, the segment will not be instantiated at all.
2.11.7     Finally, right-click on the segment EDI_DC40 and disable it (this segment is mandatory but will be filled out automatically by the IDoc adapter. Save your mapping.

LSMW IDOC MATMAS05 Material Master

Hi Experts,
Actually ,Iam using IDOC method in LSMW for Material Master Upload.
For that Iam using the IDOC type MATMAS05 .
So in the input file when Iam not the giving the Material Number IDOC is getting failed
with status 51 and giving the errors that "NO MATERIAL NUMBER
TRANSFERED".
And
if Iam giving a material number in the test file it is again getting failed
giving the error " The material does not exist ".
I am not able to understand what iam missing here.
Other than this Iam passing all the mandatory fields required .
Also in the each segment iam passing the MSGFN = '009'. i.e. to create.
Pls help.
Thanks in Advance.
Regards,
Mithun

Hi Chuin,
This forum doesn't provide specific info on LSMW. You may check https://service.sap.com/lsmw for more info.
Regards,
Markus

Help required in Idoc mapping!!

Hi,
I have an idoc to file scenario:
Idoc looks like this
Idoc
Header
E1BPE1WLMV (0.....999)
     field1
E1BPE1MALG (0.....999)
      field2
Target
Details
     field3
My requirement is that :
field 3 should b mapped to only the first occurence of field1. (and not the subsequent occurences).
     Please suggest how can i proceed ?

Thanks guys...but I have got some more inputs for my requirement now:
Source:
Idoc
Header
E1BPE1WLMV (0.....999)
field1
E1BPE1MALG (0.....999)
field2
Target:
Details
field3 (= field1)
field4 (=field2)
The Details should be created for unique combination of field1 and field 2. For e.g.
Field 1 comes 2,3,4
Field 2 comes 1,5
Then detail should be created 6 times for
field1= 2 & field2= 1
field1= 2 & field2= 5
field1= 3 & field2= 1
field1= 3 & field2= 5
field1= 4 & field2= 1
field1= 4 & field2= 5
Could you please help ?
Edited by: jayagupta21 on Apr 14, 2011 7:24 AM

Hi friends need some help in ALE IDOC !

For training purpose I am trying to create an IDOC using ALE
where I am using the same client as server as well as receiver......So I am using as receiver "NONE" . this is already present in the SM59 under logical systems..
But i cant create a port for that...as its saying its not compatible with the TRFC "
Can any one tell me what is the way to create the port ?

Hi,
You are new to ALE and IDOCs so I am giving all step by step to do the ALE.
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Just follow the procedure
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
STEP 1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
-System Name : ERP000
-Description : Sending System
-System Name : ERP800
-Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
-Client : ERP 000
-City :
-Logical System
-Currency
-Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive
to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
STEP 3) Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
STEP 4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Thanks
Sarada

Help on ORDERS05 IDoc mapping..

Hi Experts,
   Please help me out in finding out the IDoc Segment fields(ORDERS05) equivalent to the following SAP fields.
20 Quantity             VBAP KWMENG Num(6)
21 Unit of Measure VBAP VRKME      Char(3)
22 Gross Price       KONV KBETR       Curr(11.2)
23 Discount           KONV KBETR       Curr(11.2)
24 Surcharge         KONV KBETR       Curr(11.2)
25 Net Value         KONV KBETR       Curr(11.2)
26 Cost Object
31 Payment Terms VBKD ZTERM      Char                E1EDK01 -ZTERM
32 Footer Msg1      STXI     n/a             Char
33 Footer Msg2      STXI     n/a             Char
34 Footer Msg3      STXI     n/a             Char
35 Total                 KONV KBETR       Curr                E1EDS01 -SUMID (004)
       I thought for
           Quantity               : E1EDP01-MENGE
           Unit of Measure    : E1EDP01-MENEE
           Gross Price          : E1EDP01-PREIS
           But when i went to WE19 and posted the idoc by populating the above segment fields its not getting updated in the sales order, instead in the created sales order it shows quantity as 0 and its not getting updated.
     so iam not sure whether these segment fields (in ORDERS05 IDoc) are the right fit for quantity, UoM and Gross price. Please provide me the correct segment fields mapping for the above SAP fields.
     Actually Gross price, surcharge, discount and Net value are calculated automatically by SAP while creating the sales order based on the amount and quantity entered - right..? Then do i need to populate the values for these fields also in IDoc for testing using WE19.
     Please reply me.
    Thanks in advance,
    karthik.

In sales order,these quantity updating in Tatget quantity,look at VBAP Table ..
You will get good idea..
Reward Points if it is helpful
Thanks
Seshu

Help on - Multiple IDOC to single flatfile (without BPM)

I got a business need, that the ORDERS05 IDOC's should be collected on hourly basis and single flatfile should be generated for each and every hour. This scenario can be easily handled through BPM but I need the problem to be solved without BPM.
Please help me to overcome this.

hi uv,
in addition u can have a look ..
Introduction to IDOC-XI-File scenario
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
ALE configuration for pushing IDOC from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
IDOC Status
http://www.erpgenie.com/sap/sapedi/idoc_statuses.htm
Configuration steps required for posting IDocs
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
any case u need with BPM...
IDOC (Multiple Types) Collection in BPM
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
regards
biplab

Help with INVOICE01 iDoc

Hello,
I'm trying to do a MIRO from an INVOICE01 iDoc using TEST tool WE19 and function module "IDOC_INPUT_INVOIC_MRM".
I can get it to post the MIRO properly for a non taxable item but as soon as I try to post to a PO line that is taxable I get error "Balance not zero: 17.37 debits: 133.65 credits: 151.02"
This line has total invoice amount of $151.02, total amount excluding tax of $133.65, and tax amount of $17.27.
I cannot figure out where on the idoc these values need to be. I've tried every variaton I can think of and I'm stumped.
Any help would be appreciated. I need to know which records and segments I need to use. And I'm under considerable pressure to figure this out "yesterday". Thank you.
Dan

Hello;
I got the same error message. I was able to solve it by following oss note 398414.
I put below an extract of what need to be change in the customizing.
Note 398414 - EDI: processing of tax code / tax amount
Symptom
You want to edit an invoice via EDI. The invoice Idoc, however, runs into status "51" (incorrect). The system generates error message M8534:
"Balance not zero: & debits: & credits: &"
With the amount displayed as a balance, it is the tax amount.
Additional key words
idoc, idoc_input_invoic_mrm, idoc_input_invoic_mm, M8534, tax
Cause and prerequisites
Consulting
Solution
On the item level (segment E1EDP04) only the tax codes are read when the invoice Idocs are processed; the tax amounts are not read from these segments.
For each tax code, a segment E1EDK04 must exist with the total tax amount for this control indicator on the header level. Thus, the tax amounts are read from these segments (E1EDK04).
You must set the Customizing for the creation of the invoice Idoc so that the corresponding E1EDK04 segments are generated. Change this setting by using Transaction V/08. To do this you must setthe tax condition as follows: "S: Printing at totals level".
Hope it is helping.
Regards
Arnaud

Material Master IDOC MATMAS05 and unit of measure

Hi
We are using SAP standard material master IDOC type MATMAS05 to trigger IDOC. Our material master is having base unit of measure as "G". We are not using ISO unit of measurement. But Material master IDOC, segment E1MARM is populating base unit of meaurement (MEINS) as "GRM".
Any idea why IDOC is picking ISO unit of measurement instead of material master base unit of measurement.
Any idea how to send base unit of measurememt as "G" instead of "GRM" in DOC segment.
Thanks
Nilesh

Thats the way it works. In any interfacie to or from external sys. , it uses the ISO code from CUNI instead of the UOM .

Help in fulfilling IDoc Matmas05

Similar Messages

Maybe you are looking for