Creating Work Flow Item for inbound Idocs

Hi experts,
I'm just trying to create a work item in sap inbox when inbound idoc fails and gets the status 51 .Documentation says no need for any extra setup,it works with standard SAP tasks & Idoc system process codes which are all preconfigured.
I'm assiginig a user id in the partner profile.I do get a work item when there is syntax error in the inbound idoc segments(like wrong sequence of segments...), but not when idoc fails,due to idoc errors.Am i missing something.Users want a workitem when it fails,so they can reprocee/edit etc.Please help.
Thanks in advance,
Rajj

Thanks for the response.I know this task and i could see a event triggered in the event log,but no work item created in my inbox.What should i do to get the work item in my inbox.should i change this task or assign this to some thing else.
Thanks,
Rajj

Similar Messages

Need elp to create the process code for inbound idoc !

When I am creating a process code in WE42 and associating a
function module then another screen comming while saving....but in that screen in the drop down list..i didnt find the function module....how to solve ?

Hi,
Use transaction BD51 to make the FM known as an inbound FM.
Regards,
John.

Process code for inbound idoc's

hi friend,
i want to create a zprocess code for inbound idoc's pls i want to step or code.
regrads and thanks

Hi
Are you using the customised idoc i:e message type .I hope most of the data transfer techniques always has a standard message type and if you are using one such than you can check in transaction we42(inbound process code) .All the steps have been rightly been mentioned for this querry of yours if you can clearly explain as to what message type are you using and for what purpose i can send you with documentation with steps to you.At the end of the day you will be posting idocs so that the data is being reflected in the segments .The things to be noted down is :-
1.Maintain Partner Profile(we20) which is the sender system are you using ?
2.If the satus is 53 it is sucess(green ) else 64(being processed-yellow) or 51(error-red)
3.If you trigger by workflow than you have to use Message Variant .
If you are ok or incase do face any issues please do reply to the forum.
Regards
Somnath

Step-by step procedure for INBOUND IDOC (VENDOR CREATE / CHANGE)

Hi ,
Can any body provide me the step-by-step procedure for Inbound IDOCS.
As i'm new to this i need the the clarification between Inbound & outbound idocs.
How can we differentiate both?
where to define outbound & where to define Inbound?
( If possible Please explain me the procedure for Vendor Create through INBOUND IDOCS )
Thanks in advance..

Hi,
Ale Technology is SAPu2019s technology to support distributed yet integrated processes across several SAP systems.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocu2019s definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programu2019s design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocu2019s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
u2022 Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
u2022 IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
u2022 Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
u2022 Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
u2022 Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
u2022 Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
u2022 Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
u2022 Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc u2013 Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch u2013 ALE Service).
u2022 IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
u2022 Basic integrity check: A basic integrity check is performed on the control record.
u2022 Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
u2022 Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc u2013 Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
u2022 IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
u2022 IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function moduleu2019s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

Create credit memo request using inbound IDOC

Hi Experts,
I want to create credit memo request using inbound IDOC, currently I am using GSVERF03 basic type and process code GSVE, I am getting below error:
No records exist in T661W for vendor XXXXX, plant, unloading point
Anyone suggest me is this correct message type to create credit memo request or suggest me the correct one. because we are working with customer sales order and invoice not with vendor purchase order.
Thanks for your help.

ah, apologies i read outbound! I think you are using the correct message type i.e. GSVERF.
Can you not simply create the missing entry in T661W? i.e. for the missing records?

Partner profile for INBOUND IDOC

Dear experts,
Need your help to define partner profile for inbound idoc to R/3 system. There is a third party (Non SAP) based application from which idocs need to be sent to the R/3 system. There is no need to send an outbound idoc from the R/3 system. Can some one please suggest what are the steps to be taken to b configure the partner profile in the R/3 system for the inbound idoc?
Thanks,
Priyanka

Hi
This is not the right location to post this question.
You got to post this query in Data transfers section of SDN ABAP Development forums
Now regarding your question,
You need to create a Logical System with the help of the transaction SALE.
Assign the created LS to the client with the help of same transaction
Go to WE20 and create the partner with the same Logical System name
Now..as you are recieving the Inbound Idoc from external Non-SAP System, you need to maintain the message type in the Inbound Parameters by clicking on ADD Icon over there.
Before doing the above step, you got to create the connection between SAP and Non-SAP System.
Use transaction SM59 to do this. Type of connection would be R/3 I guess
Thanks
Hope it helps.

Error in work flow wait for change event

Error in work flow wait for change event of business object bus1014, Actually this business object is triggering for two transaction one is me21n and another is c201 . am trying to create fork with two branches one is create and another if change occurs wait will trigger, bt when i trigger work flow controll is not after fork, it will stop in fork only. and am not getting my workflow container variable getting instantiate, am getting error in wait. please any one get out of me in this

Hi Sangeetha
What is LV_MATERIAL? is it a BO container element? or a class element or a just a simple variable?
Error message is clear, you are trying to evaluate LV_MATERIAL but it does not contain a value.
This is a custom workflow as it begins with WS9xxxxxxx... what is LV_MATERIAL used for? what are we expecting it to hold? maybe, from event to workflow binding we can pass the value to it.
Please share the following:
1) Definition screen shot of LV_MATERIAL
2) Screen shot of The step where it is first used - from SWDD
3) Screenshot of Event to Workflow Binding
4) name of your base Business Object (seen in the triggering events tab of the WF template in PFTC)
5) What is the corresponding variable for that BO in your workflow container
6) Screen shot of WF definition from SWDD - please identify the step going in error in that screen shot
Regards,
Modak

Work Flow & Procedure For Transportation Module Of SD

Dear All,
Currently, we have just got SD implemented. Now, we shall like to go for the Transportaion Module i.e. Order Booking, delivery and the PGI followed by Auto Invoicing. Now, we wants to go for Transportation Module i.e. Shipment Creation, Shipment cost calculation , Service Order Creation etc. As we are quite new to this. So, we shall like to know the complete work flow & the procedure for implementing the same. i.e. in what sequence the various transactions to be used for Master / Transaction.
Please advise further.
With Best Regards,
Sanjeev Chugh

Thanks for the reply. Definitely, i can share the details to the best of my knowledge about the transportation module.
This module is basically meant for controlling purpose. Our main objective is to control the Transportaion Charges. Vendor Invoice must be cross verified from the sytem as well.
Our Current Business Process : As per business process, we are having fixed rates per transporter for the type of vehicle and the source - destination combination. So, whenever, we are stock transferring the material from our mfg. plants to various depots, we are using various transporters (some one are specialised for south, some are spl. for east, so on and so forth). On the receipt of the material, receiver i.e. the destination branch , confirms the material receipt.. MIGO / MIRO etc. . We wants to capture the cost of the shipment as per the system and then on the receipt of the bill from transporter, the same must be cross verified.
On going thru various documents from Web, I could gather the following details :
1. After making deliveries, we have to make a shipment document. In our case, max. time it shall be an individual Shipment i.e. Tcode VT01N. Other type of shipment be Collective Shipment, which we use very less no. of times.
2. We have to prepare Shipment Cost document by using Tcode VI01
3. We have to create a service Purchase Order By using ME21N.
In our business scenario, we shall not be using legs concept as our shipments generally used to be from point to point basis.
Sir, logically, i know our needs.. But getting stuck at a couple of points ... Like where to define various rates per transporter..That's why, i named the subject as the Work Flow & Procedure for Tpt.Module.
I shall like to request you to kindly advise further in this regard or kindly let me know if some study material is available from where i can comes to know about the exact work flow of the Transportation Module As Such.
From Where I Can Get Help on Any Tcode Usage i.e How to use a Tcode and what be its basic functionality.
With Best Regards,
Sanjeev Chugh

Sample files for inbound IDOC's( EDI)

Hi All,
I am trying to get idoc's into system using EDI , wanted sample files for inbound idocs using EDI.
If someone could send the files please.
rgds
Ajay Sharma

HI,
Here one sample file.U need to change the sender/receiver ID's accordingly to the setup at ur EDI subsystem.This 850 i/b file will create an ORDERS idoc in SAP.
ISA³00³ ³00³ ³01³006906614GE ³01³040986076 ³060714³0640³U³00401³000012157³1³P³>~
GS³PO³006906614GE³040986076³20060714³0640³5008³X³004010~
ST³850³020700691~
BEG³00³NE³020700691³³20060714~
N1³BS³ABC PHOENIX DIVISION³11³RA0290837~
N1³SU³³11³II7930501~
PO1³1³12³EA³123.45³³ND³0469520260~
PO1³2³24³EA³190.23³³ND³0469520211~
CTT³2~
SE³8³020700691~
ST³850³057796284~
BEG³00³NE³057796284³³20060714~
N1³BS³ABC RALEIGH DIVISION³11³RA0289036~
N1³SU³³11³II7930501~
PO1³1³48³EA³61.72³³ND³0469520230~
PO1³2³12³EA³123.45³³ND³0469520260~
PO1³3³6³EA³190.23³³ND³0469520211~
CTT³3~
SE³9³057796284~
GE³2³5008~
IEA³1³000012157~
Also u can check in the system and find some ORDERS
idocs and u can retrigger that from WE19.
reward if helpfulll
ram

Creating work flow

Hi all,
i am new to Work flow,
can any body tell me how can i trigger the work flow from my abap program, and how can i send the required details from the program to W/F ?
kumar

hi Narin,
i am new to WF,
it was not clear, actually i want to integrate the work flow with BPM in PI (Process Integration 7.0.
i am trying to create WF part in the SAP R/3, for the the Aproval part, because PI 7.0 doesnt have the feature User decision. So i am trying to push the data of Leave details to the WF and trigger the WF in the R/3 through a proxy program.
For creating Work flow, is Bussiness Object needed? What is the use of it, but i dont have any Business object for my Leave details, What to do?
My actual thought is,
1. create srcreen in SAP R/3, which has all the relevent fields of Leave details like emp_id, start date, end date, leave balance. i will put user commands(push buttons) like Approve, Reject, change.
In Wf this screen should apear with the leve fields with the corresponding values and push buttons.
once the manager or aprover clicks any the push buttons, in the next step the corresponding action should be done.
in this, is it possible to put the logic to capture the status of the WF like approved or Rejected? and send it back to the program in which this WF called?
Is it possible? or is there any alternative solution?
here in this i have query, how can i proceed? and what are the pre requisits to create WF?( like Busines Objects, triggring events, sep sequences, contaner elements, data base tables and structures etc.) and how do i create it?
can you give me the code? and Tcodes, to maitain events, etc....
can anybody help me?
thanks,
kumar

How To Activate Work flow Templates for Campaign Automation

Hi friends,
i created all settings for campaign Automation.when i click start process the system showing message like campaign has not started.i am not sure about weather work flows should activate for starting campaign automation.
can u please let me know how to activate work flows and what is the path to activate work flow templates for campaign automation
Thanks&regards
kishor kumar

Pls forward to me as well, facing the same problem unable to start Campaign Automation.

How to create own Web Items for Web Application Designer

Hi all,
is it possible to create own Web Items for the Bex Web Application Designer? Each Web Item has a Master Web Item and a class that is responsible for rendering data. I need a solution to get the Web Item's data - i.e. the content of a table (if Web Item = table). So my approach would be to create an own (Standard) Web Item with an own class. For example I would like to change the table's Web Item parameter <param name="ITEM_CLASS" value="CL_RSR_WWW_ITEM_GRID"/> to an own class...
Is this possible?
Or ist there any possibility to get the Web Item's data by an interface?
Any support is welcome...thanks in advance!
Best regards,
Dominik

if you want to create your own webitem check out the link given by other sdner.
if you want to be able to execute BW query using abap you can check out the following weblog.
/people/durairaj.athavanraja/blog/2005/12/05/execute-bw-query-using-abap-part-iii
Regards
Raja

EOIO should be enabled for Inbound IDocs to SAP

Hi All,
My Interface requirement:
i want to send my IDoC's to SAP ECC from SAP PI using IDoc Adapter in EOIO manner. so i have followed the below link.
http://help.sap.com/saphelp_nwpi71/helpdata/EN/96/791c42375d5033e10000000a155106/frameset.htm
1)I have have enabled EOIO in sender File adapter.
2)i have checked the Queue Processing in IDoC adapter.
assumed that IDocs are processing in EOIO manner. for proving the same, i have stopped the RFCUSER which is in ECC to process the IDOCs to SAP.
but still messages are stuck in Trfc queue, so i am thinking that EOIO is not enabled as messages are not stuck in SMQ1.
how to achive EOIO for inbound IDoCS??
Thank You,
Madhav

Hi
It's fine that messages are not stuck in smq2 on PI side. You set in smq1 system, connection and assing connetion pool numer and meesage is transfered to Ecc using common connection. On target Ecc check tcode WEINBQUEUE.
Br
Maciej

User exit for inbound idoc

could anyone please tell the user exit for inbound idoc : ACC_POSTING_GL01

I thnk the inbound idoc name is ACC_GL_POSTING01. User Exit for this is EXIT_SAPLACC4_001.
*****Reward points if useful
Regards,
Kiran Bobbala

Work Flow Software for Code

Does anyone have any suggestions? I'm looking for a software product that would help regulate programmign work flow. For example: if we have several programmers working on the same application, we want a)everyone to have the same version of the application and b)to make sure work flow of the code is, at least, somewhat regulated.
Thanks in advance

We use Starteam, it lets you assign task to people and provides source control, plus there is an ANT optional tasks for it so you can perform a checkout on a build and be sure your building the most current version.

Creating Work Flow Item for inbound Idocs

Similar Messages

Maybe you are looking for