IDoc ARTMAS Segment E1BPE1MARARTX

Hi,
IDoc ARTMAS has segment E1BPE1MARARTX
This segment is for Create and change material master data for each field.
Each field can have as per SAP
'X' Update for the field
'' No update for the field
But I see that even I do not change any field still Idoc created by setting field in this segment
as 'X'.
For Example If I create Idoc for ARTMAS without any change on arricle , it creates Idoc where
E1BPE1MARARTX- BASE_UOM = 'X' intead of blank.
Please helpm me why it happens and then whast purpose of this segment.
Thanks,
Pramod

Hi Hans,
Yes, it is possible to send each Variant separately. Actually in our environment we have the Variants coming at different times, based on the season. Like for a Style during Spring we have Yellow and Green, during holidays we do Red. So we generate different Variants at different times. Just remember to provide correct information in the segments, like <Segment>-FUNCTION field (Create / change). First time Style should have '005' and later it can have '009'.
But should be like below
IDOC1 for the generic article (with E1BPE1VARKEY segment)(New)
IDOC1 for variant 1 (with E1BPE1AUSPRT segment)(New)
IDOC2 for the generic article (with E1BPE1VARKEY segment) (change)
IDOC2 for variant 2 (with E1BPE1AUSPRT segment)(New)
IDOC3 for the generic article (with E1BPE1VARKEY segment) (change)
IDOC3 for variant 3 (with E1BPE1AUSPRT segment)(New)
Also if the client has too many variants the size of the idoc could be huge as you know ARTMAS idoc has complete information for an article.
Cheers
Kishore MVR

Similar Messages

Issue:EDI: Syntax error in IDoc (mandatory segment missing):Idoc extention

Hi all,
I have extended the the standard IDOC MATMAS05 classification view with structure as below-
E1MARAM                        Master material general data (MARA)--->Mandatory segment
     Z1KLART                        KLART --->Extended chaild to E1MARAM
         Z1CLASS                        segment for class --->Extended chaild to Z1KLART
         Z1CHARACTERISTIC               CHARACTERISTIC --->Extended chaild to Z1KLART
     E1MARA1                        Additional Fields for E1MARAM
     E1MAKTM                        Master material short texts (MAKT) --->Mandatory segment(Child   to
E1MARAM )
I am getting an error in IDOC fro material master as:EDI: Syntax error in IDoc (mandatory segment missing ).
Diagnosys By system is :*The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ZMATMAS05). However, the segment is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment is missing.
This error may have been triggered by an unidentifiable segment before the expected mandatory segment.*
Please help to resolve the issue.
Thank you.
Edited by: sanu debu on Apr 30, 2009 11:25 AM
Edited by: sanu debu on Apr 30, 2009 11:31 AM

Hi,
   You cannot add an segment in the middle of other segments.
YOu have to add any segment at the last.
If you want to add a segment as the child of another segment, it should be added after the last child of the parent segment.
In you case, you have to add your segment after the E1CUCFG segment.(NOt under that segement)
Regards,
Ravi Kanth Talagana

EDI: Syntax error in IDoc (mandatory segment missing)

HI all,
Error Message - EDI: Syntax error in IDoc (mandatory segment missing)
Status ID - E0
Message No - 072
Status of the IDoc - 26
Please help me how to solve this issue?
Thanks,
Srini

Hi,
This error normally comes up when the sequence of segments has been disturbed.
For successfully posting an IDOC you need to maintain the sequence of the segments as in WE30.
You can also check which segments are mandatory in WE30 by clicking on the segment name and the pop up that comes.
Thanks,
Manish

Determine Partner number based on IDoc Data Segments

Are there any user exits or BADI, which can be used to determine Control record parameters (Partner), based on IDoc Data segments? This is for an Inbound IDoc, into ECC.
I found EXIT_SAPLEDI1_001. But, this has only control record. It is used to determine control record parameters, by using control record only.
Thanks,
Juwin

Dear Juwin,
Could you please provide some info. about what you are trying to achieve by trying to determine the partner dynamically?
If the scenario is something like 'Partner A should get data related to only plant 1000 and Partner B should get data related to only plant 2000', you could use filters in the Distribution model to achieve this.
BR,
Aashrith

Creating own IDOC with segments

can any one let me know the steps to create Z IDOC and segments required for it.
and also the sample code (program) to poplulate the data into those segemnts from a (excel/csv file )or tables.
Thanks..

hi Aday,
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
Regards,
Naveen

Idocs n segments

what are the types of idocs and wat are the types of segments?

Hi Sunil,
   Idoc type are Two ( Tcode we30 )
1. Basic Idoc ( Ex: cremas, debmas,matmas, orders01, And Some Z Idocs        (Which you will create )
2. Extended Idoc : Theses are Generally created when you want to do any modification or enhancements to the existing basic idocs.
Segments are two
   Parent And Child will attached to parent
They may be Customised or Standard
Thanks
manju
If you are plesed, Reward points

Reg. ARTMAS segment filter

Hi friends
Any one tell me, i made some segments filter to ARTMAS in BD56. Is it effect to Other users who works on ARTMAS?. If yes what is the another way?
Thanks & Regards
Krishna
Edited by: KRISHNA DH on Sep 5, 2008 10:43 AM

Hi
It will affect only the IDocs which go to the mentioned receiver in BD56.
For other Receivers, Your Idoc will be the same as of standard.

Need IDOC and segment for mappping the sales order number

Hi,
we need the IDOC name and segment for mapping the sales order number created by oracle in sap for transaction VA01.
Whether the sales order number created by Oracle can be used to create the sales order in sap using the idoc ACC_SALES_ORDER01?
. If we can do,then what is the segment and field for the sales order number in the idoc ?
Please reply asap it's very urgent
Thanks
Edited by: suresh kumar nandhagopal on May 16, 2008 12:07 PM

Hi,
IDOC for sales order is ORDERS05. Segment E1EDKA1, for field go to SE11 and enter E1EDKA1 to find field for sales order.
Cheers.
...Reward if useful.

IDOC Missing Segment Field

Hi,
Some of my outbound IDOC's are missing a particular field in the Segment.....
This is probably because that Segment field don't have any value and hence missing from IDOC.
What can be the possible approach for Solving this probelm?

Hi Abhishek,
Can you please get the solution for such issue?
I didnt aware of Enhancement Spot...
Looking for your reply..
Regards,
Raghu
Edited by: Raghu Raman on Jan 5, 2009 1:27 PM

XI IDOC missing segment definition in type E1LFM1M

Hi experts,
we have recently upgraded our ERP system to NW 702 EH5. As aresult a new segment definition was added to our segment type E1LFM1M ( segment def. E2LFM1M007). The problem we are havign is that our XI system is still running on NW700 and it doesnt have this segment defintion. Since the upgrade we are getting an error in transaction RFC complaining about the new segment definition E2LFM1M007 everytime we try to send a vendor from ERP to SUS using BD14. Is there a way we can deactivate the new segment definition E2LFM1M007 in segment type E1LFM1M?
Thanks,
Abdul.

Hi Abdul,
Actually it does not matter what are your systems' versions, PI can always handle an IDoc properly. All you need to do is perform the following steps in your PI system:
1. Log on to ABAP stack, go to t-code idx2, find your ECC system and that particular IDoc (I believe this will be CREMAS) and delete its metadata.
2. Log on to Enterprise Services Repository, find your SWCV where the IDoc definition was loaded, and load it again from your ECC system, then activate the change.
3. If necessary, also adjust the message mapping to use/not use the new segment. Activate your changes.
Once you have these steps completed, you are ready to retest your scenario and say goodbye to the error.
Hope this helps,
Grzegorz

Flat File IDOC - ECC, segment defn x in IDoc type y CIM type do not exist

Hi,
I'm working on idoc flat file > sap scenario. Everything seems to be working up until the point where I get an error message:
EDISDEF: Port EDIPORT segment defn E2FINBU000 in IDoc type FIDCCP01 CIM type do not exist
I've loaded the meta data, and the file structure is fine. I believe the issue is related to PI not having the idoc I'm interested in listed in WE30. How do I reference the standard IDOC type FIDCCP01? Ideas I've had are around SWCV or transport from another system, the first I'm not sure which SWCV, the later seems a bit of a bodge and I dont like the idea.
Thanks
James.

Hmm.. some light for the situation. Seems that the segments imported are:
E1FINBU     E2FINBU     31I
E1FINBU     E2FINBU001     40A
E1FINBU     E2FINBU002     40B
E1FINBU     E2FINBU003     45A
E1FINBU     E2FINBU004     45B
E1FINBU     E2FINBU005     46A
E1FINBU     E2FINBU006     46C
Which indeed does not have E2FINBU000, which the IDOC is most definitely trying to pass. I can only guess that the middleware producting this IDOC is flawed, and that standard SAP ALE will accept this as E2FINBU (It works into another SAP system without XI).
Guess I've answered my own question, but feel free to offer light for points
Thanks,
James.

IDOC ORDERS05: Segment E1EDPA1Doc.item partner information is not filled

Hello,
I'm working on the AFS-Retail Interface for Orders.
In the first step we create a sales contract in AFS with the combined demand from a retail purchase order and in a second step the sales order call-offs which are the Retail orders for the stores (NB; one PO for one store).
The problem is in the sales order call-off. In the Retail outbound IDOC the information about the relevant ship-to stands only the header segment E1EDKA1 (PARVW = WE).
In the AFS IDOC inbound the ship-to is written in the header partners of the sales order. But because the information is missing on item level the information is copied from the sales contract which leads to the wrong ship-to for the items in the sales order.
For the communication we are using the basic type orders05. Is there a possibility to fill the item partner segments E1EDPA1 out of the standard or do I need to implement an user exit in the Retail IDOC outbound process so that the partner information is filled also on item level?
Thanks in advance.
Regards,
Christine

Hi Christine
I am working on SAP AFS 6.0.. I Had same issue.....When sales order ref to a contract....i resoved it
u need to write user exit for this....
Ramesh

Mapping issue: Two different IDOC P19 segment to one flat file line

Hello,
Scenario: For each P01 segment (without uepos) in an order idoc I want to create one line in a plain text file.
Problem: One P01 segment has two P19 segement with different qualifiers. I want to map both P19.IDNTR (with different qualifiers) fields to the same record in my plain text file.
How can I do this?
My "if statement" does noet work. I check the qualifier in the P19 segment. But when one field in the record of the plain text is filled with an P19.IDTNR the second P19.IDTNR field is empty.
Please advice.
Best Regards,
Erik van Lisdonk

Erik,
you should get both values if you change the Context of your INPUT-Fields one level higher (for the IDTNR and for the Qualifier that is checked in the IF-statement).
The Context needs to be set to P01 for all fields and I assume it is set to P19.
Greetings
Stefan Hilpp

IDOC extension (segment cannot be identified)

Hi all,
I have IDOC DEBMAS configured, but when I trigger 1 customer from BD12, the IDOC is failing with status 26 error segment cannot be identified.
In WE82, we have the following:
DEBMAS DEBMAS06 470
DEBMAS DEBMAS06 ZDEBMAS06 470
I only need the standard structure without extension but we have one interface using the same IDOC with extension.
In the partner profile(WE20), i set DEBMAS in the message type, DEBMAS06 in the basic type, and blank in the extension.
What could be missing in the configuration?
Thanks,
Nene

Extension segment is being populated in the user-exit. Only insert extension for specific output type. Closing this thread.

IDoc - Get Segment Definition or Version in Code

I'm working on the ABAP-PI Port, created a FM based on FM OWN_FUNCTION now.
In my FM, there is a call to a function
CALL FUNCTION 'EDI_SEGMENTS_GET_ALL'
that retrieves all the segment data for a particular IDoc number.
However, it returns only the segment name EDIDD-SEGNAM and not the segment definition.
Example:
Value returned: "E1EDKA1" ( EDIDD-SEGNAM , 27 char long field)
I'm actually looking for the Segment Definition that goes up to 30 characters long.
Value I need to be returned: "E2EDKA1001" - has the extra 3 digits at the end that represents the Version.
If you go to WEDI, Development > IDoc Segments, You can see that the Segment definitions belong to a data type EDISEGDEF (30 characters long).
Does anyone know how I can get this programmatically?
The IDoc file downloaded by the FILE port stores the 30 char Segment Definition in the file
Using the ABAP-PI it only returns the segment name (27 char)

Hi all,
Thanks for your replies.
EDISDEF might be useful, but I'm not sure how to use it at the moment.
I am supplied in the code a structure of type EDIDC, which has the following values (not all are listed)
MANDT C 3 308
DOCNUM N 16 0000000000002050
DOCREL C 4 640
STATUS C 2 03
DOCTYP C 8
DIRECT C 1 1
RCVPOR C 10 SUBSYSABAP
RCVPRT C 2 B
The above represnets a particular IDoc being processed (see DOCNUM and DOCREL)
The default code then uses a FM to get the segment data based on the DOCNUM.
CALL FUNCTION 'EDI_SEGMENTS_GET_ALL'
 EXPORTING
 DOCUMENT_NUMBER = I_EDIDC-DOCNUM
 TABLES
 IDOC_CONTAINERS = I_EDIDD
 EXCEPTIONS
 DOCUMENT_NUMBER_INVALID = 1
 END_OF_DOCUMENT = 2
 OTHERS = 3.
Does anyone know of any FM that returns a EDID4 (has 30 char segment version) structure instead of a EDIDD structure (27 char seg def)?
And the value EDIDC-DOCREL (SAP Release for IDoc) e.g.
640
does not match up with values available in EDISDEF-RELEASED (IDoc development: Release of segment definition), e.g.
30F
40A
45A

How can I find if the segment definitions are
E2EDKA1 or
E2EDKA1001 or
E2EDKA1002 or
E2EDKA1003

IDoc ARTMAS Segment E1BPE1MARARTX

Similar Messages

Maybe you are looking for