XI sending # chanracter in null IDOC segments

Hi,
We are doing a File to IDOC scenario. We are picking the file through FTP using a file adapter. The File contains data in XML format of ORDERS.ORDERS05. On R/3 side it is received as an IDOC (type ORDERS.ORDERS05).
However in R/3 we see that the IDOC contains # in fields
in which no value is entered.
The IDOC cannot be processed in R/3 because of # caharacter.
Looking forward for help and guigance in resolving this issue from all SDNites

Thanks Sidharth,
This note is for SAP Web AS 620. We have XI 3.0 on SAP Web AS 640.
Regards
Vinay Rane

Similar Messages

Adding field in standard IDOC Segment E1EDL24

Hello Friends,
I have an urgent requirement that I have to extend IDOC segment E1EDL24 with two fields PABNR and LFSNR.
When I tries to change the segment in WE31, it shows an error message that you can only modify the segments of customer namespace and cannot modify Standard IDOC Segments.
Can we modify the standard IDOC segments, and if yes, how can we modify the standard IDOC segments. Please clarify.
Points will be rewarded generously.
Regards,
Navin

Hi Naveen,
We cannot Modify the Standard segments. But we have to Create a new Segment and Add these fields.
Then Create an Extended Idoc type
Implement User Exits in Outbound And Inbound ..
This is the Complete Steps and Info on this...with an Example...
Enhancing ALE
For example, if in an outbound interface you find that the IDOC type does not contain all the data you need to pass to the other system, you can extend the IDOC to accommodate the additional fields and enhance the ALE function modules to populate the fields. Similarly, if in an inbound interface, there is additional data that needs to be posted to the R/3 application, you can extend the IDOC type to have additional fields populated by the external system or translator or the other R/3 system and then enhance the inbound ALE function modules to post the additional data to the R/3 application.
let us use the SAP Customer Master application as an example. Specifically, letâs focus on the IDOC extension and ALE function module enhancement of IDOC type DEBMAS02 and message type DEBMAS (Customer Master) and the IDOC reduction of message type MATMAS.
IDOC EXTENSIONS
Letâs first look at the concept of IDOC extension. SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02, ORDERS02, and WMMBID01. By extending the Basic IDOC type, you are actually creating a new IDOC type. You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type.
Note that you should not add fields to existing segments but should create a new segment and associate it with an existing segment. This, in a nutshell, is the process of creating IDOC extensions.
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address (see Figure 1), DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
Determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save.
Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
2. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
From transaction WE30 or WEDI go to Development -> IDOC Types.
Enter ZDEBMASZ for Object Name.
Click on IDOC Type.
Click on Create.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter a description.
Enter.
You will see a display of the composite IDOC type with all segments, including Z1SADRX (see Figure 3).
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
3. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
Click on Display <-> Change.
Click on New Entries.
Enter DEBMAS for message type.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter your SAP R/3 release number for Release.
Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
4. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
From transaction WE30 or WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object name.
Click on Extension Type.
From the Development Object menu select Check.
Repeat the operation for IDOC type ZDEBMASZ.
A check log will be generated for each run with details of correctness or errors (see Figure 4).
In some situations it is possible to receive errors during the check process, especially segment length errors. The incorrect IDOC segment can be repaired and corrected by executing program RSEREPSG. This program checks the formal consistency and repairs incorrect segments. In test mode it will generate a log of formal correctness for the specified segment only. For the program to repair segments in normal mode, the underlying IDOC structures (DDIC structures) must be active. This program rectifies the lengths of the DDIC structures and not the fields themselves. RSEREPSG can also be used to change the person responsible for the object and the release flag.
Menu paths may vary slightly depending on the release/version of SAP R/3, but the procedures and the principles are the same.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
Error handling is a very important consideration when making enhancements to inbound ALE/EDI objects. In ALE and EDI inbound processing, workflow is used for handling errors at different levels such as technical and application. If workflow has been configured for the interface, the error messages and workflow items flow to the inbox of the named recipient(s).
It is also critical to enhance the workflow that handles notifications of the inbound ALE/EDI process. In most scenarios this is not a very difficult task because SAP lets you influence the workflow parameters and messages in function exits (customer functions). You typically do this using flags and message codes to trigger certain workflow actions. If you conform to the status codes and flags stipulated for workflow processing, the enhancement could be error-free and seamless. In the case of an inbound IDOC with an extension, you should populate the EDIDC fields IDOCTYP (new IDOC type) and CIMTYP (extension type) accordingly.
Reward if Helpful

EDI IDoc Segment Filtering Transactions

Hi All,
Is there any transaction for EDI IDoc segment filtering where partner profile is set up with partner type as 'customer' or 'vendor' (and not partner type as 'logical system' where ALE IDoc segment filtering transactions BD59 & BD64 can be used) ?
Thanks !

Thanks Lokeshwari.
Actually, a perticular field in an IDoc segment needs to be filtered. e.g. I dont want to send idocs with a perticular item category for ORDERS05 IDoc.
Is there any transaction to fulfill the same ?

Fill IDOC segment, E1IDBW1. For PEXR2002 Basic Type

Hello Team.
We send the IDOC for the Basic Type PEXR2002, Message Type PAYEXT.
This IDOC doesn't fill the Segment E1IDBW1 (IDoc header - special instructions (INP) )
I'm review some notes(1164524) and said to fill this segment it's neccesarie config the IHC.
But doesn't have this functionality.
It's possible fill the segment E1IDBW1 in a user exit or any other enhacement at creation idoc moment?
My idea is used the FM
CALL FUNCTION 'GET_SEGMENT_POS_FOR_INSERT'
    EXPORTING
      I_BASIS_TYPE            = ch_edidc-idoctp
      I_EXT_TYPE              = ch_edidc-cimtyp
      I_SEGMENT_TYPE          = 'E1IDBW1'
    IMPORTING
      E_INDEX                 = li_tabix
    TABLES
      IT_EDIDD                = t_edidd
    EXCEPTIONS
      BASIS_TYPE_NOT_FOUND    = 1
      EXTENSION_NOT_FOUND     = 2
      EXTENSION_ERROR         = 3
      INVALID_IDOC_DEFINITION = 4
      IDOC_ERROR              = 5
      INVALID_SEGMENT_TYPE    = 6
      INVALID_START_INDEX     = 7
      NO_MORE_POSITION        = 8
      TOO_MANY_SEGMENTS       = 9
      OTHERS                  = 10.
To Fill 2 constants in this segment.
Do you have any other idea?
Thanks
Edited by: David Lezama Gonzalez on Sep 1, 2011 2:51 PM

Hi,
Basically the segment E1IDBW1 will always be filled via user exit.
If you work with the IHC (In-House-Cash) application you have to fill
the E1IDBW1 segment as described in note 626577.
If you don't work in an IHC environment the following conditions must
be fulfilled:
1. The payment program has to fill certain fields (e. g. REGUH-DTAWS,
REGUH-DTWS1 - REGUH-DTWS4).
2. If this is fulfilled the payment data (REGUH, REGUP tables) will
be filled. The instruction keys will be moved to IDOC segment
E1IDKU3.
3. In user exit EXIT_SAPLIEDP_002 you can take over the instruction
keys from segment E1IDKU3 into E1IDBW1.
You may also read note 496663, this note explains about user exit
EXIT_SAPLIEDP_002 to populate this field in the idoc.
Also, you can check the note:
580321 - RFFOEDI1: BTE process 00002441 (Change IDoc)
REgards,
Cristiano

The XI does not send messages with correct IDOC structure

SAP XI 3.0 sends to ECC IDOC HRMD_A07
The XI does not send messages with correct IDOC structure.
In XI Design, Software Component RHEVOLU, Ive imported the Objects
HRMD_A.HRMD_A07 from SAP ECC; In Tools -> Export Reduced XSD, I saved
HRMD_A.HRMD_A07.xsd in Namespace http://suezambiental.com.br/HR . At
Message Mapping -> mmAdmissao, in Imported Message -> Import XML or
XSD, I imported the reduced Idoc file generated above, mapping source
fields to target fields.
The IDOC sent from XI to ECC has this structure (template: 22122)
E1PLOGI
E1PORIG
E1PITYP
E1P0000
E1P0001
E1P0002
Status 53 -HR: ALE inbound processing for HR master data
But does not update HR Master data.
The structure expected in ECC side (template: 20376) is:
E1PLOGI
E1PORIG
E1PITYP
E1P0000
E1PITYP
E1P0001
E1PITYP
E1P0002
Status 53 -HR: ALE inbound processing for HR master data
By using WE19 transaction, this structure was changed manually; so, the
HR Master data was updated.
Witch kind of customizing or correction could be made in XI, to send
the correct structure to ECC?
Best Regards
Claudio

Hi Claudio,
In your case, there are perhaps two causes:
1. perhaps when you have import the idoc, for a strange reason, a bad metadata was created by XI. You can clean this one in tcode <b>IDX2</b> (Idoc metadata cache).
2. but it's also probably an error in your Message Mapping. Have you correctly manage segment E1PITYP?
Regards
Mickael

Idoc Error - EDI: Syntax error in IDoc (segment cannot be identified)

Hi All,
have created a new reduced message type for our new vendor A/C group through BD53. Also done reqd config for sending the vendor master through this message type. .
I have created couple of vendors for testing with X01 with withholding tax functionality and when try to send these vendors , Idocs are getting failed .
When I create vendor without withholding tax functionality , idoc is getting posted succesfully . If create vendor with entries in the feild whih are related to withholding tax . Idocs are getting failed .
If I see the status in WE05 ,Idocs which are posted succefully are showing the basic type as CREMAS03 . For idocs which are getting failed have the basic type as CREMAS04 and also the extension as Z1CREMAS . I don`t understand why the system is defaulting CREMA04 & Z1CREMAS when I send the vendor master with withholding tax feild entries.
I am not much familiar with ALE /Idoc set up. Please can any body help me to resolve the issue.
The error message in we05 as below
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment Z1LFA1M does not occur at the current level of the basic type CREMAS04 (extension Z1CREMAS).
This error can have several reasons:
The segment Z1LFA1M is assigned to a group whose header segment does not occur.
The segment Z1LFA1M does not exist in the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
Thanks

Hi,
I don`t understand what do you mean release after adding segment.
Message type works i.e. Idoc get posted if I send with the vendor w/o withholding tax field entries. Idoc fails when send vendor with withholding tax field entry.
Regards

IDOCS: Segment Definition and Segment Type

Hi Gurus,
We are working on IDOCs and trying to send a Location Master IDOCs to Third party system.
1. In the IDOC print preview we are in a position to see the IDOC segment type Ex: E1TPLOC but customer is asking for Segment definition E2TPLOC.
When we go through the documentation:
u2022     Segment Type consists of Segment definition with Version and Release.
u2022     Segment Definition will contain the Field names
u2022     E1TPLOC, E1TPDLH, E1KNVAM, E1TPTRM & E1TPSHH Segment types with concerned Segment definitions are
                     E2TPLOC,E2TPDLH, E2KNVAM
How to see the Segment definition types?

Hi,
You can see the documentation in the transaction WE60 by giving the IDOC Basic type and extension if you have any.
E1 and E2 are the same, when you see the definition of the segment the naming convention will be E2 and when populating the data it will be E1.
I believe he is asking the segment definition alone, you go to WE60 transaction and give the inputs and click the parser button and that will give you the definition of the idoc and which you can share it with your partner.
Thanks,
Mahesh.

IDOC Segment Definition received instead of Segment type

Hello Folks,
When i send a Z Idoc Segment from A to B System, It is successfull from A System, but in B System sometimes its erroringout because in the inbound idoc Segment Definition is coming instead of Segment type.
For Example
From A System I have sent Z1P0002 segment
B System I have received Z2P0002000(Which is the segment definition for Segment type Z1P0002)
Any inputs to above problem?

Hi,
The problem may be due to system B using a older release version of the IDoc. In those scenarios, even though your IDoc type is recognized, it may not be possible for the reciever to determine the right segment version of the reciever.
There are options in the WE20 partner profile configuration, Field Segment release in IDoc type and Segment Appl. rel. which enable the partner system preventing from erroring out.
BR/Yogesh
Edited by: Yogesh Surender on Jun 1, 2009 12:34 PM

IDoc segment not reaching XI

Hi,
I have a peculiar problem where the values populated in an IDoc segment are not coming to XI, though the values are visible in the sender SAP system, they are not present in the IDoc XML generated in XI.
Please help if someone faced a similar problem.
Thanks
Pushpinder

Hi,
Check if problems are raised on Cache of Design side of your IB.
Environment - Cache Status Overview
Then "Clear Data Cache".
And try again.
Regards,
Giuseppe

Procedure to find mandatory field in an IDoc Segment

Hi all,
Please guide me to find mandatory field in an IDoc Segment.
Ex: I went to MATMAS05 IDoc type. I know that E1MARAM and E1MAKTM are the mandatory segments for MATMAS05 IDoc Type.
But, I would like to know what are the mandatory fields for E1MARAM or E1MAKTM segment.
Please guide me to find mandatory field in an IDoc Segment (for the above example).
Thanks,
Sudarsan

hi, here I have a good suggestion to solve your problem.
Assuem you are research which field is mandatory in your mastr data inbound. Let's suppost it's a material. You already known how to create it in online t-code, which field should be filled, which view should be inputed.
Then, configure you material related IDOC for outbound, make sure that system will send out a material IDOC to other partner system (it can be a dummy system)when you create it.
Then check the sent IDOC, you can find out how SAP system fill the IDOC according to your input.
You can get to know how to fill your IDOC in this way.

CRM IDOC Segments Changing in PI mappings

Hi All,
I had configured a scenario from CRM to PI and to SQL Table.
When ever a BP is Created or Changed an idoc with that BP is sent to PI and to SQL. I had used this IDOC(CRMXIF_PARTNER_SAVE) for mapping.
When i send BP of Person type the IDOC Segment is getting Changed and Mapping error occurs.
So please suggest me whether to use IDOC or not?
Is there any Adapter i can use for real time?
I need to get data of BP automatically.
Thanks in Advance.
Sriram

Did you try change pointers..........
Regards
Ravi Raman
PS: Points..are the only rewards here...so..!!!!!!!

IDOC segment fields prefixing blank space with values

Hi Experts,
I am sending data through custom IDOC from SAP to XML which generates successfully but getting 2 problems in the data.
its having 3 level idoc segments:
SEGMENT1 with 1 field (field_name(20))
SEGMENT2 with 3 fields, (code_g(20), field_name(20), value(20))
SEGMENT3 with 4 fields, (code(20), field_name(20), Language(2) & text(20))
When i check the idoc in WE02,
1. i found that segment2-value field is prefixing some space along with the values.
    Eg: if the output is "0111" whihc is plant, in the output (WE02) it is giving "       0111"
2. Segment3-language is no where in the output and text which should come as "011" is coming like "       EN011" means it is concatinating language field value and displaying it with the text field value with prefixing space.
This is happening in PRD not in QA & DEV. I also checked the transport req and everything, Its same everywhere.
Can anyone please help me on this.
Regards,
Nik

Hi,
This issue happnes when u are moving the data to iDOC segement with offset.
to aviod this improper move instead of using offset statement use below mentioned code.
decalare a structure as
Data SEG1 type SEGMENT1 ,
        SEG2 type SEGMENT2,
       SEG3 type SEGMENT3.
then while moving
SEG2-code_g = 'XXXX'
SEG2-field_name = 'YYYY'
SEG3-value = 'ZZZZ'
here u are moving the segment values to idoc data (SDATA) and then append it.
move seg3 to idoc-sdata.
then append it to idoc.
hope this helps

Idoc segment numbers

Can anyone tell me how idoc segment numbers/order are determined? I have a rather large ORDERS05 idoc being used to send outbound EDI 850 documents. This line sequence number is kept in segment E1EDP01, element POSEX).
For smaller purchase orders (20 lines or so) the idoc segment sequence follows the same order as the purchase order line numbers (0010, 0020, 0030 and so on). This means that E1EDP01, POSEX = 0010 followed by 0020 etc.
But in one of my larger idocs POSEX is beginning with 00220, goes up consecutivelt to 00410, then goes to 00210, then to 0010 - 00200. I can't find any obvious sort order in this.
Any insights will be greatly appreciated. Thanks.

Ram,
Create a File port in WE21 and assign this port to your IDoc in WE20. When the Idoc is triggered the corresponding IDoc is converted into IDoc Flat file with fixed lengths. Then you can read this fixed length Idoc and can convert into Idoc XML. or Check the section 3.2 which converts your flat file idoc into Idoc XML. This should solve your issue.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
---Satish

Incoming IDOC-Segment missing

Hi, Friends,
I have a strange problem.
The incoming IDOC in idx5 list miss a segment although the meta data is renewed.
Could sb. help?
Thanks and Reguards
Zhiping

Hi Krishna, Hi Jakub,
I tried both. But it remains.
Still strange is, the ALEAUD idoc with Z-Segment containd in E1PRTOB-Segment produced by the sending system contains some E1STATE segments. But the number of ALEAUD idocs recieved in IDX5 list is the number of the E1STATE segments in sending system. And every recieved ALEAUD idoc contains only one E1STATE-Segment
Why is it splitted? and where?
Thanks
Zhiping

Edit Std. IDoc Segments

Dear All,
Hope you guys are doing good.
I have a requirement where i have to change the field length of IDoc DELVRY05 segment E1EDL24 Release 700 for the field LGMNG from 15 to 9.
Can someone tell me how can i achieve this?
Regards,
Raj

Hi ,
Follow the steps for custom Idoc type creation .
1.Business Case
SAP R/3 systems send out data through IDoc (Intermediate Document), which in internally has segments and fields containing the data. But sometimes, these fields are not sufficient for a specific end-to-end business scenario as far as data transfer is concerned. So in such scenario, either few fields are to be added or subtracted, or completely new structure- IDoc needs to be created. This are called as Custom u2013 IDOC Types. Following blog gives out step-by-step approach for creation of the same.
2.Development of IDOC types
2.1 Creation of Segment Types
Run T-code u2018WE31u2019 to create segment type, which has fields to contain the data and are added to the segment type in the same transaction. The data stored contained into the segment mesh is finally stored in EDISEGMENT table.
Add your custom fields as per business scenario.
To make it available to other transactions, release the segment created.
Go to Edit -> Set Release
2.2 Creation of IDoc type
Run T-code u2018WE30u2019 to create custom IDoc type. Enter the name of custom IDoc you want to create and click on red box for creation.
Now, it takes you to following screen. Here you can add description for your IDoc type. Also you can specify name of existing IDoc for Copy or Successor mode.
Now, you can maintain attributes of the custom IDoc, which consists of attaching segment type created above to the IDoc type. Also specifying the details of frequency of these segments getting filled i.e. Maximum and Minimum number. Fill the necessary details and release this IDoc type as well.
2.3 Creation of logical message types
Run T-code u2018WE81u2019 to create the logical message types. Go to Edit mode and click New Entry to go to following screen.
Save the entered data.
2.4 Linking Message type and IDoc type.
Run T-Code u2018WE82u2019. Now we have to link these created IDoc types and Message types. Enter the message type name, Basic IDoc type (ZCUST_IDC) and release type to be linked. In the data transfer through ALE, these message types represent the IDOC structure.
Extension field above will be used as per the Extended IDoc type scenario i.e. in case of addition of few more fields into the existing IDoc type.
<<text removed>>
Thanks
Shambhu
Edited by: Matt on Jun 30, 2009 10:43 AM - don't ask for email addressses please.

XI sending # chanracter in null IDOC segments

Similar Messages

Maybe you are looking for