Inbound Processing : BOM-Position deleted

Hi Experts,
I'm using a self-made program to distribute Material-BOMs and Changes.
To explain the problem, here is an example:
I have the following BOM in the Source system:
BOM 1234.567.890 ( at Day 0 )
-- Pos. 0100 - TEXT - Text-ID
-- Pos. 0110 - STOCK ITEM - 9999.888.888
-- Pos. 0120 - STOCK ITEM - 9898.999.999
I made a Change into this BOM, by adding a new position:
BOM 1234.567.890 ( at Day + 1 )
-- Pos. 0100 - TEXT - Text-ID
-- Pos. 0110 - STOCK ITEM - 9999.888.888
-- Pos. 0120 - STOCK ITEM - 9898.999.999
-- Pos. 0130 - STOCK ITEM - 8888.888.999
Now I want to distribute it.
I send the first version ( Day 0 ) by using 'MASTER_IDOC_CREATE_BOMMAT' with MESCOD = 'CRE' and DATUV / ALE_DATUV = STKO-DATE.
Then I send the "Change" version ( Day + 1) with MESCOD = 'CNG' and DATUV / ALE_DATUV = AENR-DATUV.
In the Target system, the BOM is OK at Day 0. At Day + 1, I see the new position with his change number, but the Text-Position has been deleted ?!?!?!?!?
We are using Text-Objects (ID) into Text-Positions. But in the Target system, we don't have these Objects.
Is it possible that the Inbound Processing for BOMMAT IDoc check if the Text-Object exist, and if not, delete the position ?
Rewards for support. Thanks.
Regards,
David

Hi Gordon,
I've decided to copy Function idoc_input_bommat and to make some modifications and now it works fine !
I think the standard function isn't ok.
Regards,
David

Similar Messages

Inbound Processing : Error when changing a BOM

Hi Experts,
I have the following error when I send a BOMMAT IDoc in "Change" Mode (Editing the BOM, to recreate the History inthe Target system) :
Start processing in API: CSAP_MAT_BOM_MAINTAIN
Group BOM
Changes to the BOM exist after 03.11.2008
Date 03.11.2008 copied from change number
Item (1) 0040 L 000000001084237016 000000000000000000000000 cannot be uniquely identified
Item (3) 0100 L 000000001084237021 000000000000000000000000 cannot be uniquely identified
Item (6) 0200 L 000000000768041196 000000000000000000000000 cannot be uniquely identified
End of processing in API: CSAP_MAT_BOM_MAINTAIN
Any idea ?
Regards,
David

Hi Gordon,
I think I found something.
When I create a BOM with ALE in the Target, no problem. Then when I want to update it, I've got this error ...
In the Source, we're working with Text Object for Text Item (INCLUDE Text ID). But in the Target, Text Object doesn't exist, and when we update or modify the BOM via ALE, the Inbound Process try to find the old Text Object before updating it with the new one ...
I think the solution is to create all Text Object/ID (Ta SO10) in the Target ... I don't understand why the ALE Inbound Process doesn't create Text Objects if they don't exist...
Regards,
David

Steps in Inbound Processing in ALE IDOC

Hi all,
Could anyone explain the steps to be followed in inbound processing in ALE Idoc.
I know we have to create a FM n then call that in a program. But still the detail steps are not clear.
An example will be really helpful.
Thanx

Hi
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
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
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

BPM workflow "In Process"-Queue "Permanent error in BPE inbound processing"

Hi All,
I am trying to collect messages from 2 different interfaces into BPM( Integration Process).
when I checked in sxmb_moni , i found the error on outbound status & BPM workflow has stuck with status "In Process".
it is not showing any error in Workflow, how to solve the issue.
due to the above error, other messages are stuck in Queue stating "Permanent error in BPE inbound processing".
Please help.
-Jyoti

Hi Jyoti,
Goto T.Code swwl, in that clear all fields and choose from date as 1 month ago and try to execute. Then, delete all entries there. And re-execute your scenario.
In this case, please see SAP Note 1126656.
Please see the below blog, it might be helpful to you.
/people/henrike.kaiser/blog/2009/02/03/how-to-analyze-stopped-queues-in-xi-ccbpm
Regards,
Rajesh

BPM: Permanent error in BPE inbound processing

Hi guys...
i am having a problem in my scenario which is involving BPM.
The problem is when i execute the interface it is showing green flag aginst PE in sxmb_moni and in smq2 one queue is showing with sysfail and BPM: Permanent error in BPE inbound processing error.
yes..i searched on SDN and found resources like Note number 1126656
i checked al the steps which were earlier mentioned posts like:
SWWL: there are no entries existing
SMQ2: cleared the queues ,regenerated but still no luck.
My undertsanding is no work is being generated at all .
I checked BPM with F7 : its correct no errors
BPM has return code of 0 in sxi_cache
In ID BPM is latest and refreshed.
Is there any way i can overcome this problem.
Your inputs will be of real help.
Thanks in advance.
Regards,
Kiran.

My undertsanding is no work is being generated at all .
If you are getting the error for Source ---> BPM flow then there is a possibility that the ID objects (RD, Interface determination) are to be blamed.
1) Recreate these particular ID objects/ make some dummy changes
2) Activate and ensure that Cache is refreshed
3) Delete the entry in the queue (or delete the queue)....do this only if the XI system is not of Quality, production
4) some times the BPM cannot be triggered from sending a test message from RWB .... so make a testing from the source application .... this particular case has heppened to me and hence suggesting to you.
Regards,
Abhishek.

Error In inbound Processing IDoc

Dear All,
I am facing error while inbound processing of IDoc
In status record of IDoc following errors are occuring
Status 60 : EDI: Syntax error in IDoc (mandatory segment missing)
The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ). However, the segment is missing in the IDoc
Status 51: Application Document not posted
Log details :
Error : Material Number should be filled.
When i checked IDoc all 4 fields in E1MAKTM have the values in inbound IDoc.
Please guide me how to resolve these issues so that IDoc will be posted and Material Master will get created in reciever system.
Thanks

Hi Praveen,
I checked the data in IDoc for this segment.
It is ok as required in basic message type.
e.g. the error says that mandetory segment E1MAKTM is missing.
when i check basic type
MSGFN : Function
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
SPRAS : Language Key
internal data type : LANG
Internal length : 000001 characters
Position in segment : 002, Offset : 0066. external length : 000001
MAKTX : Material Description (Short Text)
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 003, Offset : 0067. external length : 000040
SPRAS_ISO : Language according to ISO 639
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 004, Offset : 0107. external length : 000002
is information.
and data in segment of IDoc is
MSGFN     005
SPRAS     E
MAKTX     MANATA2000 TEST ALE
SPRAS_ISO     EN
which i think is ok.
I have no clue why this syntax error is coming.
Thanks
Niketan

Permanent error in BPE inbound processing error

Hi guys...
i am having a problem in my scenario which is involving BPM.
The problem is when i execute the interface it is showing green flag aginst PE in sxmb_moni and in smq2 one queue is showing with sysfail and BPM: Permanent error in BPE inbound processing error.
yes..i searched on SDN and found resources like Note number 1126656
i checked al the steps which were earlier mentioned posts like:
SWWL: there are no entries existing
SMQ2: cleared the queues ,regenerated but still no luck.
My undertsanding is no work is being generated at all .
I checked BPM with F7 : its correct no errors
BPM has return code of 0 in sxi_cache
In ID BPM is latest and refreshed.
Is there any way i can overcome this problem.
Your inputs will be of real help.
Thanks in advance.
Regards,
Seshagiri.

Hi Praveen,
If the BPM goes in error due to "The incoming payload structure is incorrect (not matching message type structure of abstract interface)" , is there any work around?
Currently in my scenario BPM goes into error due to incorrect structure , error show up in SMQ2 . And the subsequent message also get stuck. What I have to do is to delete the queue in error and reactivate the queue manually.
Is there any way we can avoid this situation.
Thanks,
Pankaj

IDoc to Soap, with BPM - Permanent error in BPE inbound processing

Hi Experts,
IDoc to Soap, with BPM - > Permanent error in BPE inbound processing
How to rectify this any issue???
Thanks-
sk

Hi,
The inbound processing encountered a permanent error and the queue therefore stopped.
The error message "Permanent error in BPE inbound processing" may be caused by the following:
- At the start or when you process a process instance, the inbound processing encounters an exception that was not handled. This exception is triggered, for example, by a transformation step, a synchronous send step or a control step but it was not caught in an exception handler branch. If the exception that was not handled occurs in the first transaction of the started process instance, the system does not write the process instance to the database but it sets the queue that has this error message to the error status.
Refer to the help in Note 1082099
- The inbound processing triggers this error if the correlation evaluation shows that a message should be delivered to a process instance that has the status "error". Since delivery to process instances that contain errors is not permitted, the queue is stopped.
Use the simulation of the message delivery in the detail view of the relevant queue LUW to determine the relevant process instance for the affected message and use transaction SXMB_MONI_BPE "Continue Process Following Error" (or transaction SWF_XI_SWPR) to continue. If you cannot continue the process instance, check whether you can logically delete the instance. In this case, use the method that is described in Note 807906 to logically delete a process instance.
Check whether your system contains other process instances that have errors in order to detect similar problems. Use transaction SXMB_MONI_BPE "Continue Process Following Error" or transaction SWF_XI_SWPR.
Use the report RSWF_CRL_MAINTAIN to check all of the correlation instances in question or the relevant process instances that you can reach using "Display Work Item".
- Messages that cannot be delivered because no correlation instance can be found may lead to the error that is mentioned here. Check whether the causes that are outlined in Note 1094028 affect your case.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful.

LSMW idoc Inbound Processing settings

Hi,
We have done LSMW with BAPI method to create Bank master.
In Idoc Inbound Processing settings -
We created partner type as 'B' i.e, for BANK
While creating Partner Number it is not allowing to create Partner Number. The error is "Enter a permissible partner number"
Please let me know what would be the problem.
Regards,
Hari
Edited by: Bhatlapenumarthy Hari Krishna on Sep 12, 2008 9:31 AM

Hi,
Use patner type as US only and LSMW as Patner number.
this will surely solve your problem .
plz do this way :
The first requirement is a file port for the file transfer. If required, create a port of the file type via Maintain ports. To do this, position the cursor on "File" and press Create. You should be in change mode. SAP recommends:
Port: LSMW
Name: Legacy System Migration Workbench
Version: 3 (IDoc record types SAP Release 4.x)
Outbound file Please enter a (dummy) physical directory and a file name, i.e. u2018filelsmwu2019 ·
As an addition, you can specify a tRFC port. This port is required, if you do not want to create a file during data conversion but submit the data in packages directly to function module IDoc_Inbound_Asynchronous.
SAP recommends:
Port: assigned by the system
Version: 3 (IDoc record types SAP Release 4.x)
RFC destination: Name of R/3 System
Name of port: Legacy System Migration Workbench.
Then the partner type should be defined or selected. SAP recommends:
Partner type: "US" (User)
As of release 4.5A, this partner type is available in the standard system. Up to release 4.0B inclusive, this partner type is not available in the standard program and should be added. SAP recommends:
Partner type: Create US
Report name: /SAPDMC/SAP_LSMW_PARTNERTYPES
Form routine: READ_USER
Short description: any.
Finally a partner number should be defined or selected. SAP recommends:
Partner number: LSMW
Partner type: US
Partner status: A (active)
Type: US
Language: DE or EN
Person in charge: Your user ID.
Activate IDoc inbound processing
reference : help.sap
thanx.
Edited by: Dhanashri Pawar on Sep 12, 2008 7:10 AM

Problem in Inbound Processing

Hi
I am using Inbound Processing using WE19.
It is showing "Partner profile not maintained". However I have maintained in WE20 & added Msg Type in Inbound Params.
After generating IDoc, in WE05 its showing status Red & showing message -
Partner profile inbound not available
Message no. E0337
Diagnosis
An inbound partner profile could not be found with the following key:
/PROCLNT100/LS//MATMAS01////
This involves the key fields of table EDP21.
I have checked in Table EDP21, entries for that Partner Profile exists.
Please help.

Hello Nikhil and other Experts,
I neeeeeed your guidances. Thank you all in advance. I am explaining what I have done so far in the following!!
Scenario: 1) Same system: T05
               2) Two clients: 454 and 455
               3) Two logical system for sure: T05CLNT454 and T05CLNT455
               4) Transfer Material Master Data from 455 to 454
Since I am a student and this system is actually for me to play around and practice, I did something crazy. I have been browsing so many forums and taking so many actions, but still I am having some issues.
What I have done:
1) Went to 'BD10' on 455 -> Tried to send material master data
2) 0 Communications generated for IDOCS
3) Googled the solutions and found out that it was due to filter setting.
4) Went to 'BD64'. Since message type for transferring Material Master is MATMAS, I went there trying to inactivate those annoying filters for message type MATMAS.
5) I could not inactivate those, so I deleted them intentionally, even though the system warned me not to delete so. The technical names of those two filters I deleted were 'MM-PUR1' and 'MM-PUR2'
6) Later, I created another filter, which was related to MATMAS, without activating it, or say without setting ANY filtering parameters.
7) I did the same things on 454. (Deleted two filters and created another one called TEST)
8) Went back to 455 and went to 'BD10' again.
9) 50 IDOCS generated.
10) Went to 454 and used 'BD11' to received material master data. Was not able to receive any.
11) Used 'WE02' on 454, and those IDOCS were all showing error 56. (Red message)
12) Used 'WE20' to define partner profiles on both clients, 454 and 455. (I actually just did whatever I felt like to do, since this system was only for me to practice. I don't mind messing it up. Haha~~)
13) Went to 455 again and used 'BD10' to send my materials again.
14) Back to 454 and used 'WE02'. This time, some (about 8 IDOCS) were green and 42 IDOCS were yellow with message 64 (IDOC ready to be transferred to application)
15) Executed 'BD11' on 454, and there were exactly 8 materials being transferred.
16) Re-did 'BD10' on 455 and 'BD11' on 454 many times, but it seemed that there were no chances to successfully receive 50 IDOCS on 454. In other words, there were still yellow messages each time.
Some suggestions from other forums said that we could increase the number of "dialog work process". I am just wondering is that the root cause to my situation now?
Any other clues from you experts? BTW, if some of you see what I was doing was crazy, please correct me as well. For example, step 5, deleted two filters directly without a doubt. Haha~~ (Maybe you can tell me how to inactivate them?) Thank you soooooo much in advance!!
Best best regards,
Alfred

QRFC Inbound processing example using JCo

Hi Freinds,
1. I am trying to set qRFC queue for Inbound processing, in order to process on IDoc from external system.
Queue when I say regsiter, it shwos as status Starting, its not showing active status.
2. is tehre any JCo example which can be used to comunicate from Java program to qRFC?
Thanks

Hi ,
I have registered qRFC queue name, and able to see records entering in qRFC queue scheduler.
when I process LUWs in queue, its processing successfully.
I am not able to understand the behavior of QueuePosition now.
I tried with queuePosition 2,1,3,2
but,in the queue, when I see records, ther are entered with time, not with queue position number.

Permanant Error in Inbound Processing in BPM

Hi All,
i have done a File1->JDBC(Synch)->File2 scenario using BPM.
It works fine when i have data in input file ie File1. However when my input file empty my scenario shows green flag in "OutboundStatus" and in queue gives error "Permanant error in Inbound Processing". When i tried to see the error in details got exception in START_PROCESS....
After deleting this entry from queue and sending file with data it works fine.....
I just want to know why it happens....? My input file can be empty as i am using it for triggering the scenario.
Do i need to do any settings in BPM or scenario to handle this?
Thanks,
Atul

hi atul,
in the rec step where u set the start process check box, you give the message. it is this message that is used to start the BPM process and not ur input file... the input file is used to trigger ur scenario not ur process. therefore u have exception in 'start process'.
hope it helps.
regards,
latika.

ALE INBOUND Process Code

Hi,
In ALE INBOUND Process Code Apart from the Function Module name, what are the important things to be filled up while creating that InBound process code in WE42. What is the importance of those? what is the importance of Object Attributes in that?

Hi Mahesh check this may be useful to you
The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.
Link Message Type to Function Module (WE57) Client independent
u2022 Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)
Define FM settings (BD51) Client independent
u2022 Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)
u2022 Click on New entries
u2022 Enter 0 for mass processing in the output column
u2022
Maintain process codes (WE42) Client dependent
A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.
To maintain the process code follow these steps:
u2022 Log on to the appropriate receiving system client
u2022 Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)
u2022 Choose Inbound with ALE service
u2022 Choose Processing with function module
u2022 Click on Processing with function module and choose create icon
u2022 Click on New Entries
u2022 Type in process code XXXXXXX and give it a description and save
u2022 Now you are asked to Please maintain codes added in ALE entry methods, enter and choose XXXXXX and copy it. You should choose a FM similar to your one.
u2022 Enter your process code XXXX
u2022 Enter your function module XXXXXX
NOTE: The next 6 steps are used in workflow error handling.
u2022 Enter IDPKFIDCMT in object type
u2022 Enter MASSINPUTFINISHED in End event
u2022 Enter IDOCINVOIC in IDoc object type
u2022 Enter INPUTERROROCCURREDFI in IDoc start event
u2022 Enter INPUTFINISHEDFI in IDoc End event
u2022 Enter IDOCINVOIC in Application object type
You will need to determine the task associated with object XXXXXXXX, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.
To set up the workflow area please consult the Workflow config guide.
Create inbound partner profile
For each message type you need to maintain the inbound partner profiles.
Maintain receiving system partner profile (WE20) Client dependent
To maintain inbound partner profiles read the document ALE configuration procedure:
u2022 Add the message type XXXXX with process code XXXX.
u2022 Enter the output mode (background, immediately) for inbound processing and NO message code.
Test
Once the inbound function module has been debugged the scenario should be ready to test in its entirety. If problems occur, read through the relevant areas of this document to check your configuration or code.
You can find all the inbound and outbound processcodes in we64.
Regards,
SMS.

Inbound process of ALE------- get point.s

Hi all,
In WE05 i m able to see my idoc with status 03. Now wht i need to configure further for the correspoinding inbound process, to see my data on the receiver system.
Regards,
[email protected]

Hi
See this and do accordingly
Application Linking and Enabling (ALE)
In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients
For our purpose we have two clients
namely Client 100 and Client 200.
System name is SAPKDC (FOR BOTH 100 AND 200 CLIENTS).
Distribution of Material Master Data Between two Systems
1) SETUP LOGICAL SYSTEM: (Note: Do Not Create This Step)
To do this follow the following steps
Execute SALE Transaction Code
On The Screen Click on Sending and Receiving Systems.
Then Click on Logical Systems.
Then Click Defining Logical Systems.
Click New Entries Button
(E.g. (LG100 sending system)
(LG200 receiving system))
Enter two logical system names and their description.
Save
Comeback to SALE Transaction Code screen.
2) Now you have to allocate the created logical systems to respective clients.( Note: Do Not Create This Step)
LG100 assign to client 100
LG200 assign to client 200
To do this, do the following.
Click Assigning Client to Logical System.
Ignore the message that comes up on the screen.
Select client 100
Click details button on the toolbar icon or press F2.
In the logical system box, enter LG100.
Click on the save Icon
Click the back button.
Now select client 200.
Click details icon or press f2.
In logical Systems box, enter LG200.
Save
Back.
Comeback to SALE Transaction Code screen.
3) Maintain RFC Destination: (TR.CODE:SM59)
(Note: Do Not Create This Step)
Click Create Button on the Screen
On the Screen Maintain RFC Destination i.e LG200.
Enter LG200 in RFC destination box.
Connection type is 3
Give a description for the RFC destination.
Maintain Technical Settings on Details on Technical Settings tab
Target Host as : SAPKDC (NOTE: Save it as a Host Name)
Maintain Logon Details on Logon/Security tab.
Language: EN.
User: MMUSER200 (This is the logon for dist.)
Client : 200
Password: MM1234.
Save.
Click on create to do the above process for Client 200 in
The client 200 system.
4) Maintain Distribution Model.(BD64). (ABAPer role starts here)
Execute Maintain distribution model directly for
creating the model.
Click on change mode button on App tool bar of the Screen.
Create Model View pushbutton on App tool bar of the Screen.
A pop screen will appear in which you specify
Short text as Distribution for MM Data.
Enter Technical Name as LGMODEL.
Select Model View and Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as LGMODEL.
Sender as LG100.
Receiver as LG200.
Again Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as LGMODEL.
Sender as LG200.
Receiver as LG100.
SAVE.
On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Logical System as LG200.
Then execute the screen.
Click back.
Again On the same screen goto Menubar and select EDIT.
Again select Model View and then select Distribute.
****LOGIN to client 200.
Execute Tr.code BD64 and again On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Model View as LGMODEL
And Specify the Logical System as LG100.
Then execute the screen.
Click back.
*******Switch back to client 100 Session.
5) Create Material using MM03 Tr.Code.
Enter the material name as LGMATERIAL
Industry sector as Mechanical Engineering
Material Type as Finished Products.
And then Click on Data Pushbutton on the App tool bar.
Select views.
In the select views box for materials check basic data 1 AND 2.
Click enter icon.
In the next screen that you get
Give the text of the material as NEW MATERIAL.
Base unit of measure as KG.
Gross Weight as 200.
Net Weight as 100.
Weight Unit as KG.
In the description area language (E) and material description.
Click Save.
Now I Created a Material in Client 100 , I want to transfer this data to Client 200.
6) Execute BD10 to transfer the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client100).
Then a Screen will be displayed in which it shows that
1 Master Idoc Generated .. Enter
1 Communication Idoc Generated..Enter.
*******LOGIN to Client 200.
7) Execute BD11 to get the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client200).
8) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
If not follow these steps.
9) Execute Tr.code WE19( for rectification of errors in client200).
Specify the Existing Idoc Number and Executes it .
A Screen is displayed in which you specify the corresponding Function Module as INPUT_IDOC_MATMAS01 and execute it.
10) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
Now the Material is correctly displayed in Client 200.
11) Monitoring of IDOCS.
Transaction Codes:
IDOC Display of Status: WE 05.
IDOC Date and Time: WE07.
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
<b>Reward points for useful Answers</b>
Regards
Anji

Find flagged process orders for deletion

Hi all ,
How do i find flagged process orders for deletion ?
i need report or t-code

Hello,
Try with t-code COOISPI. In selection,Put material no and system status(sel. at header level) as DLFL
and also check "with deeltion flag indicator"
Check with result and revert.
Regards,

Inbound Processing : BOM-Position deleted

Similar Messages

Maybe you are looking for