BD64 filter IDoc with Z-Segments

Hi,
i made a customer extension to the cremas05 idoc and set a filter in the BD64 at E1LFA1M (first level).
If the filter is true - the Idoc will be created through BD14
If the filter is false - an error appear through BD14.
"internal error: Program read_table ....data_select_for_block"
After disableing the user Customer Exit (creation of the z-segment) ... the process is running fine with filter true and false.
Is it not possible to filter an IDoc(extension) with an zsegment ?
any ideas ?
Regards,
Gordon

Hi Gordon,
BD95 Define Filter object type .We can specify the field and the table it belongs ... It is used to create a new IDOC Type or IDOC Extension ....
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
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
ALE Configuration
ALE
ALE
Reward points if useful
thanks
karthik

Similar Messages

How outbound IDoc with Z segment is creating without using a program/FM?

Hi,
I am having an outbound IDoc with Z message type and segments.
I need to find how this IDoc/ IDoc segment is getting created. I tried to find
it using the segment’s where used list (in SE11- IDoc segment structure). But it
is showing that the structure and fields are not used anywhere.
How it is possible to create a Z segment in IDoc without
using the corresponding structure in some program or function module?
I have searched in google/scn for a solution, but didn’t find
anything.
Any one please helps me to find how this IDoc segment is
populating?
Regards,
Dipin

Hi Arthur,
This IDoc is catering as part of a flow (Tcode IW21). I have
set a break point in the function module ALE_IDOCS_CREATE and processed the transaction
IW21, but the program didn’t stop in the break point, but the IDoc got created.
Regards,
Dipin

IDOC with Multiple Segment to One Single Record Mapping

Hello
I have a problem mapping the values of the segment <E1CSKTM>
which occurs two times in my source IDOC to a single record.
My requirement is to get one field (LTEXT) from the first E1CSKTM segment and map it to Name and take the same field (LTEXT) but from the second E1CSKTM segment and map it to OrgDescription
The source message:
<?xml version="1.0" encoding="UTF-8"?>
<COSMAS01>
 <IDOC BEGIN="1">
 <EDI_DC40 SEGMENT="1">
 <TABNAM>EDI_DC40</TABNAM>
 <MANDT>300</MANDT>
 <DOCNUM>0000000000750131</DOCNUM>
 <DOCREL>700</DOCREL>
 <STATUS>30</STATUS>
 <DIRECT>1</DIRECT>
 <OUTMOD>2</OUTMOD>
 <IDOCTYP>COSMAS01</IDOCTYP>
 <MESTYP>COSMAS</MESTYP>
 <STDMES>COSMAS</STDMES>
 <SNDPOR>SAPQAE</SNDPOR>
 <SNDPRT>LS</SNDPRT>
 <SNDPRN>QAE300</SNDPRN>
 <RCVPOR>SAPQAX</RCVPOR>
 <RCVPRT>LS</RCVPRT>
 <RCVPRN>QAX304</RCVPRN>
 <CREDAT>20080308</CREDAT>
 <CRETIM>090820</CRETIM>
 <SERIAL>20080211134325</SERIAL>
 </EDI_DC40>
 <E1CSKSM SEGMENT="1">
 <MSGFN>005</MSGFN>
 <MANDT>300</MANDT>
 <KOKRS>1000</KOKRS>
 <KOSTL>0105012501</KOSTL>
 <DATBI>99991231</DATBI>
 <DATAB>19000101</DATAB>
 <ERSDA>20060219</ERSDA>
 <USNAM>HAMEED</USNAM>
 <BKZER>X</BKZER>
 <BKZOB>X</BKZOB>
 <PKZER>X</PKZER>
 <MGEFL>X</MGEFL>
 <BUKRS>1000</BUKRS>
 <GSBER>20</GSBER>
 <KOSAR>N</KOSAR>
 <VERAK>TBA</VERAK>
 <WAERS>SAR</WAERS>
 <KHINR>105012001</KHINR>
 <KOMPL>X</KOMPL>
 <OBJNR>KS10000105012501</OBJNR>
 <PRCTR>0105012000</PRCTR>
 <FUNC_AREA>Z240</FUNC_AREA>
 <FUNC_AREA_LONG>Z240</FUNC_AREA_LONG>
 <E1CSKTM SEGMENT="1">
 <MSGFN>005</MSGFN>
 <SPRAS>A</SPRAS>
 <KTEXT>مدير الدائرة وموظفوه</KTEXT>
 <LTEXT>م. د. وموظفوه/ حسابات منطقة المدينة</LTEXT>
 <SPRAS_ISO>AR</SPRAS_ISO>
 </E1CSKTM>
 <E1CSKTM SEGMENT="1">
 <MSGFN>005</MSGFN>
 <SPRAS>E</SPRAS>
 <KTEXT>DvM and Stff/AOD-Mad.</KTEXT>
 <LTEXT>Div Mgr and Staff/AOD-Madinah</LTEXT>
 <SPRAS_ISO>EN</SPRAS_ISO>
 </E1CSKTM>
 </E1CSKSM>
 </IDOC>
</COSMAS01>
The Target Message:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:CostElementMT xmlns:ns0="http://se.com.sa/materials">
 <INSERT>
 <COSTELEMENT_DATA action="INSERT">
 <TABLE>usmuser.OrganizationCodes_test</TABLE>
 <access>
 <OrgCode>105012001</OrgCode>
 <CostCenter>0105012501</CostCenter>
 <OrgDescription> English Name<OrgDescription/>
 <Name>Arabic Name</Name>
 </access>
 </COSTELEMENT_DATA>
 </INSERT>
</ns0:CostElementMT>
is this possible using the graphical mapping?

Hi Baheej,
If in your input "E1CSKTM" segment always occurs twice than u can go with the above UDF mentioned by Chirag and also u need to take care that field (LTEXT) also always occurs.If the field does not occur always than you need to check it using exists functions.
Andmoreover if the "E1CSKTM" segment does occur more than twice than u need to create a UDF where u need to pass the values alternatively.
Please check the above details and let us know if any furthur enhancements are to be made.
Thanks,
Bhargav
Note:Award Points if found useful.

Generating an IDOC with all segments filled every time

IDOC Experts,
I am new to IDOC/ALE and I am struggling with the following situation.
I am trying to create an ALE interface with a Transportation Management System. I have been able to configure ALE and IDOC to generate an IDOC XML file for message type DEBMAS. I have activated change pointers and I am seeing the changed customers when I run RBDMIDOC.
The problem is the external system will require the complete data every time the customer master is changed. Right now I am only seeing the changed segments in the IDOC file.
Is it possible to configure SAP to populate all of the segments every time a DEBMAS IDOC is generated?
Thank you in advance for any direction you can provide.
Brian Snyder

Hi Brian,
I tested my system and it does not work,I guess we can't set up mandatory.
I think if you know any user exit for that application,then fill the segments programtically.
Sorry for wrong information what i provided.
Thanks
Seshu

Issue In processing an IDoc with Huge Segments

Hi All,
When we are trying to process an Huge IDoc which has large number of segments. The IDoc process starts and stops in the middle and remains in 64 status ( there are no short dumps etc).
Currently the IDoc is configured to be Trigger Immediatly. However when we schedule the same IDoc in a background the IDoc is processed successfully.
So wanted to check what might be the reasons for Idoc to stop the process in between.
Regards,
Swaroop

Possible reasons :
- Huge memory consumption
- Large processing time for Idoc segments .
Idoc parsing and processing happens inside a LOOP statement around EDIDD table , now if you have larger no of segments this will lead to larger execution time .
There may be other performance reasons e.g. Read Table without Binary Search ; check the IDOC processing function module code .
Also check the SAP notes for the IDOC processing function module code ; just mentioning a similar SAP note 381942 .

Filter IDoc segments

Hi,
in a HRMD_A IDoc I want to transfer segment E1P1001 only if field RSIGN equals 'A'.
What are the steps to configure this scenario?
Please describe the steps instead of sending me links (as I know them already).
Thanks and regards
Patrick

hi Patrick,
you can do this with the ALE distribution model Filter.
1. Go to BD64
2. edit mode
3. choose your model
4. choose your IDoc
5. apply filter
6. if your filter of field RSIGN is not available go to BD95 and BD59 to apply it first.
7. enter "A" as filtervalue.
Save and go for it.
IF there is an IDoc with Value RSIGN = A then the segment is existing, if not ... the segment will be deleted.

How to isolate error with a record/segment in IDOC with multiple records

I have an IDOC with multiple records/segments (typically 1000 records/segments). Sometime XI can not process the IDOC because of some control characters in data.
1. How can I pre-processed the IDOC to remove those control characters?
Can I use XPATH expression/Java class to do it? How can I configure the XPATH expression/Java class in XI to pre-process the file?
2. Until I have answer to 1st question. I would like to find out the error is exactly for which record? What configuration can I do in XI to isolate the error is with which record/segment in IDOC?
Thanks in advance.

Split the IDoc.
with in the UDF, after the validations if every thing fine, pass as successful records to success_MT and pass it to target system using Branching in BPM.
if errors found in the record, then store the error records in Hash table with in UDF, get the IDoc number, frame as a string and raise alert.
U have to do this in the context of IDoc.
If U wanna get the IDoc Number, Segment Name and field name for every failure, U can pass the expected error field name as constant to UDF, frame the sentence in the UDF like -> IDoc 1234321 segment SEG001 field FLD03 has a special character *.
If U wanna pass this string to source/target, U can do in error messages branch in BPM.
U must use BPM for splitting the IDoc, since it is multi-mapping.
reg.,
Yallabandi.

Data Transfer using LSMW IDOC processing with multiple segments

we need to post the document data (Header structure, BP item structure, G/L item structure..etc) using LSMW IDOC processing.
is it possible to transfer data for all these structures (Segments) in single file?

Thanks for the reply.
I am assuming when we are specifying the file in LSMW we are going to give the option to generate the file with include all structures.
could you please elaborate further is there any thing specific we need to do while configuring LSMW to get the file for all segments in the IDOC with field names which we are going to populate with data, so that we can use it for data transfer.
any help document will be helpful.

Configurations required in SLD,IR,ID,SM59,BD64 to Start with IDOCS

Hello all,
Can You Post me the Above details.
thanks,
Srinivasa

Hi Srinivas,
Let us explore the need for each steps and detail it now...
Step-1 : You need RFC destinations for placing the metadata of the IDoc.
Use transaction SM59 to maintain an RFC destination for the IDoc sender/receiver system.
This RFC destination is used to retrieve the IDoc metadata from the sender system.
The IDoc adapter needs these metadata to create the corresponding IDoc-XML message from the RFC stream.
Step-2 : Next You need IDx1 for getting IDoc metadata from the Sender system.
Use transaction IDX1 to assign a port (RFC destination) to the system that contains the metadata of the IDoc types.
Note:
There is a mechanism on the Integration Server that uses this RFC destination to retrieve and cache the metadata at runtime if it is not yet available on the Integration Server.
Nut-Shell:
Since IDoc metadata is cross-client, you should only assign one port for each system.
If several ports are assigned, ensure that they are all working.
This is Done in Partner Profile.
If you are not able to load the metadata from this system (because of administrative or security-related restrictions, for example),
you can also load it from a reference system (for example, a test system) and use transaction IDX2 to assign it to your production system afterwards.
For non-SAP systems, either the ports in transaction IDX1 have to point to a reference SAP system, or you copy the metadata with transaction IDX2.
I come to mean that if you double click the OutBound Parameter in the Partner Profile you will be allowed to choose the Idoc type like Matmas,Debmas blabla..
There after providing the receiver destination in that partner profile which is nothing but your Maintaining Metadata through a port,
which on double click leads to RFC destination alloted with a port to transfer its data from sender to receiver Server.
Step-3 : Goto SLD and do the following.
Access the System Landscape Directory (SLD) to maintain the technical systems for the sender and receiver business systems of your system landscape.
You have to define a technical system (and a client in the case of SAP systems) to which your business system belongs.
When you define a client number, you also have to specify the corresponding logical system name in the Technical System Browser.
Note:
The technical system configuration is not required if your business system is configured as a data supplier for the SLD.
Step-4 : Goto Integration Directory and do the folllowing.
Access the Integration Directory to define your business systems as services without party.
a) Either you can choose from the Objects Business Service where your client is defined for it.
With this Selected Business Service you just rightclick and choose ASSIGN TO BUSINESS SCENARIO.
b) Second choice is to choose the business system which was done in SLD.
Do the receiver determination and interface determination but since the adapter is not required to choose for Idoc dont do sender determination.
Note:
The IDoc adapter only uses the service definition (business system) together with the corresponding adapter-specific identifiers in the Integration Directory.
The maintenance of your IDoc sender system in the SLD is therefore not sufficient.
It is recommended that you assign your business system definition retrieved from the SLD to a service in the Integration Directory.
Nut-Shell:
Using this information about the system ID, client, and logical system name for a specific business system, the IDoc adapter is able to specify the corresponding service in the XML header. Routing is then based on service names.
You need the
 logical system, SAP system ID, and client for an IDoc receiver SAP system
 SAP system ID and client for an SAP system
 logical system for a non-SAP system.
This means that the business systems used for the routing definitions in the IDoc-XML message header are retrieved from the adapter-specific identifiers of the service definitions in the Integration Directory,
where for each business system client, the corresponding system ID, client, and logical system name is defined.
Caution:
Use the import function to retrieve the adapter-specific identifiers for a service (business system) to avoid double maintenance in the SLD and Integration Directory.
Step-5 : Steps in Integration Repository.
Export the IDoc in Imported Objects.
Double click the Idoc to view the structure.
This Idoc type is decided in the partner Profile.
See step-3 for further details.
Create the Interface Objects like
1.Data Type for Receiver File.
2.Message type which wrapps this Data type.
3.Interface Type.
a) For Sender Idoc just drag the Idoc name which you have loaDED IT IN YOUR imported objects.
b) For Receiver File It just wrapps the Message type of the file.
4.Message Mapping:
The Fields selected in the data type for the file should be the mandatory fields in the Idoc.
Since the Idoc is in the sender side,it just performs similar operation like selecting things from a database.
Begin and Other Attributes are neednt be worried to map.
The Mandatory fields which was chosen will need to be mapped with the target file.
5.Interface Map:
Just Wrapps the Message mapping.
Step-6 : BD64 is to Distribute the Idoc to Various Acceptors.
1.Create Model View.
2.Add Message Type to it.
3.So that it displays your model view with your Message type like MATMAS.
4.Goto Environment and click Generate Partner Profiles.
5.Executing it,you will get a log indicating the Partner,port and Outbound Parameters.
6.After Doing this goto Edit Menu available in the tool Bar and give Distribute.
7.After distributing it ,it shows your logical system name along with the technical name.
8.Now to fill the IDOCs with Data we have to go to Transaction bd10.
9.We can give our own selection criterias and select the list of materials accordingly.
10.Now to check whether the IDOCs has been correctly created and sent to the receiving system (in this case it is the SAP XI Server)
11.we have to check it out in Transaction WE05.
12.Now we can go to the Location we specified in the Configuration where the file will be created.

Sales Order Outbound IDOC - Restricting Items being created with a Segment

Hi,
I have a requirement to restrict segments being created for Items (Child) in Sales Order Outbound IDOC based on conditions in the Items (Parent & Child). Can you please suggest me a suitable solution?
Basic Type: ORDERS05, Message Type: ORDRSP. What is the IDOC Function Module to be used to create Outbound IDOC for Sales Order?
Appreciate Your Help.
Thanks,
Kannan
Edited by: Kannan SA on Jan 3, 2008 3:03 PM

Hi,
if the segments are mandatory then you can't trigger the idoc without those segments.
Otherwise, you can read the segment and clear all the data in it, the segment will not be attached to the outbound idoc.
Where to do it? Search the CALL CUSTOMER-FUNCTION '002' for the outbound idoc for example IDOC_OUTPUT_INVOICE for Invocing.
Regards,
Baburaj

Filter Idoc for 4.5B

Hi experts,
I'm working on a very old version, the 4.5B.
I'd like to make filters for Idocs:
On ECC6, it can be done with transaction BD64, what about 4.5B?
Thx,
Regards
Mehdi

remove the filter in BD64..
and add the manual code in the include ZXM06U02, by rasing exception not to create idoc and sent to external system..
use the below synatx for raising exception..
Read table int-edidd with key segment = 'E1MARCM' .
MOVE int_edidd-sdata TO XE1MARCM.
if XE1MARCM-werks ne 'requiremtnt'.
This statement stops the Process to create idoc..
RAISE DATA_NOT_RELEVANT_FOR_SENDING.
Endif.
Prabhu
Edited by: Prabhu Das on May 14, 2009 6:52 PM

IDOC with a step by step example w/o ALE

Hi All,
Can anyone send me the step by step document with screenshots on IDOC without using ALE : .
Thanks in Advance,
Tejo Ravi

Define and setup for user developed IDOC
Define segments: WE31
Create new basic idoc type: WE30
Create message type: WE81
Link message type to IDOC basis type: WE82
Create RDC destination: SM59
Create logical system: SALE
Create port: WE21
Create partner profile: WE20
Set up distribution model (If necessary): BD64
1. WE31: Define segments
Transaction code: WE31
Create segment Z1ACTIV
Own segments should start with Z1..Z2u2026.. instead of E1..E2u2026..
Segments must be released before they are transported
2. WE30: Create new IDOC
Transaction: WE30
Create new idoc ZHRACT01. The idoc uses segment Z1ACTIV
Note: Same idoc can exist in different versions e.g. ORDERS01, ORDERS02u2026..
The difference between versions is that tehre are more segments in newer versions.
3. WE81: Create message type
Transaction WE80
Create new message type ZHRACT01
4. WE82: Link message type to IDOC basis type
Link message type ZHRACT01 to idoc baisi type ZHRACT01
5. SM59: Create RDC destination
6. SALE: Create logical system
7. WE21: Create port
8. WE20: Create partner profile
9. BD64: Set up distribution model (If necessary)

Issues in IDoc Sender Scenario:IDoc with errors added

Hi all
Am working on an IDoc to JDBC scenario. In R/3 system, I have created distribution model, partner profile, RFC destination and port.The IDoc is generated and is sent to XI successfully. But in XI , there is no entry in SXI_MONITOR for this (unfortunately IDX5 is not available in the XI server! ;as of now). Instead an entry is made in WE05 and WE02 with stautus 56(IDoc with errors added). In the status record:
status 56 : External segment name E2KOMG003 cannot be interpreted
status 60 : Basic IDoc type COND_A03 could not be found.
And the segments displayed in data record are different from the segments in the data record of the IDoc generated at R/3. (say for E1KOMG at R/3, E2KOMG003 in XI).Earlier the flow was working fine and the DB table was updated successfully. And the entire stuff is believed to be 'unmodified' .
Would any one help in resolving the issue.
Thanks,
Chilanka

Hi,
>>>>I have created partenr profile in R/3.Need I create a partner profile in XI for R/3 system?
no you cannot create any partner profiles in XI
for more about IDOC configuration in XI check :
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Creation of IDOC with message type INVOIC01

Hi All,
I am trying to create a new IDOC with message type INVOIC01.
When I see transaction WE81, I observe that the required message type INVOIC is available. Also in WE82 the basic types INVOIC01, INVOIC02 and INV_ID01 are attached to the message type INVOIC.
However, while trying to create an IDOC in WE19 using a message type, I get options to create against INVOIC02 or INV_ID01. The basic type INVOIC01 is not getting populated because of which all the IDOC that I create are of basic type INVOIC02.
The client wants me to create IDOCs with basic type INVOIC01.
Can anyone please help?
Thanks in advance.
regards
Nagarajan

Hi Nagaraj!
I've looked at the documentation and did not find information, which would help me. Should I use in my case z-segment to put extra lines or there is some qualifier in segment E1EDP02 (Document Item Reference Data), which triggers to another referencing (not PO or delivery note)?
Thank You,
Natalija

How to generate PAYEXT (PEXR2002) IDOC with many invoices for same vendor

Hello,
We are implementing the IDOC payment processing through transaction F110. The first test we ran using multiple items for the same vendor created an IDOC with multiple E1IDPU1 segments for each invoice. We then configured a second bank and ran the test again. This time the multiple invoices for the same vendor generated a seperate IDOC.
Does anyone know where I should start looking to figure out what I did wrong? We are hoping to generate 1 IDOC for all invoices for the same vendor.
Thanks,
Brian

Hello,
May I know how or what are the steps you did to create multiple invoices and generate multiple idocs for the same vendor? I have a requirement to generate multiple payext idoc for a single vendor.
Please advise. Thank you very much!

BD64 filter IDoc with Z-Segments

Similar Messages

Maybe you are looking for