Finding workitem for a certain idoc

Hello,
is there a way to find a woritem for a certain error idoc. Using SWI1 is extremly slow. There must exits a direct link
between the idoc and the workitem. When I delete/book a error idoc in BD87 the corresponig workitem disapears from SO01.
Ralf

I found a solution:
a possible way to do it is transaction SWI6.
for a ORDERS Idoc enter
Object type cat,: BO
Obect type: IDOCORDERS
Obect key: Idoc number
Ralf
Edited by: Ralf Schäfer on Feb 16, 2010 12:22 PM

Similar Messages

Where to find dtd file name/schema for a certain XML Gateway interface

Hi folks,
For a certain XML Gateway interface, in which DB table can I find the dtd file name and dtd schema that this interface use?
Now I can find its map name.
Thanks.

Hello!
I found the answer myself now.
The XLST files are part of the static web content of the MI project Visiprise.
In the SAP MII workbench go to the project Visiprise
Then under the tab Web the static contecnt can be found under the folder WEB/XSLT/..

Oracle 10g - To find the corresponding record for a certain row

Hi all,
The scenario is like this - Suppose I've got a table with 100+ columns. For a certain row inside, I need to find its corresponding record which is in the same table. The way how I define "corresponding" here is - these two rows should be identical in all attributes but only different in one column, say "id" (primary key).
So how could I achieve this? What I can think of is to fetch all columns of the first row into some pre-defined variables, then use a cursor to loop the table and match the values of the columns of each row to those variables. But given that we've got 100+ rows in the table, this solution doesn't look practical?
Any advises are greatly appreciated. Thanks.

something to play with as Solomon suggested (use some other string aggregation technique if you're not 11g yet)
you'll have to adjust the column_list accordingly
select 'select ' || column_list ||
       ' from ' || :table_name ||
       ' group by ' || column_list ||
       ' having count(*) > 1' the_sql
from (select listagg(column_name,',') within group (order by column_id) column_list
          from user_tab_cols
         where table_name = :table_name
       )Regards
Etbin
Edited by: Etbin on 25.12.2011 16:53
Sorry, I'd better leave the forum: the title says you're 10g :(
Providing a link for replacing listagg: http://www.sqlsnippets.com/en/topic-11787.html

Workitem is not generating for an Inbound Idoc

Hi All,
The problem I am facing, when inbound idoc is processing in SAP, if there are any errors occurred, it would generate a work item and that will be sent to user Inbox (SBWP) as per the workflow. Here it is not generating a work item for an inbound idoc where is there is an error. So user is not receiving work item mail to inbox, to check about the idoc error. This idoc has been processed through the function module.
Could you please let us know your input on this issue.

Hi Hitu,
The problem could be at multiple places.
To debug check the workflow which sends the workitem to the user when an error occurs.
Check if this workflow is getting triggered when the error occurs. If yes, then check the step whre this workflow fails.
Else, check the event linkage of this workflow and check if the associated event is getting triggered or not. If yes, check if the event linakge is active for the workflow.
There could be other places as well to diagnose the error.
Check if these inputs gives you some direction.
Regards,
Saumya

Where to find documentation for RFCs / IDocs?

Hi all,
We're planning to implement some XI interfaces against the MM module - where can we find online docs for available RFCs/IDoc APIs?
Thanks very much in advance!
Steve

Hi,
have a look at this page:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7c9f43d711d1893e0000e8323c4f/frameset.htm
to find many MM interfaces: invoices, orders etc
some are not well documented (material movements)
so just ask an interface consultant about them
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Finding Exists for IDOC

Can anybody Please tell me the list IDOC Enhancements for the Basic IDOC type TPSSHT01 i need to use Enhancement IDOC for this.

check the enhancements present in the IDOc type SHIPPL
check the function module
IDOC_INPUT_SHIPPL, Global search for Call customer-function
V56I0010
V56I0003
V56I0002
V56I0001
V56I0006
V56I0004
etc..
For message type SHPCPR,IDOC_INPUT_SHPCPR
similarly for this also..

Any FM/Bapi/program to find BAPIs for tcodes?

Hi,
Is there any program or BAPI or FM to find all the BAPIs that are used in Tcode.
Thanks
Ganesh

There is no such report, and it will be hard (via ABAP) to determine which BAPI should be used for a certain transaction. These BAPI's are normally not used in transactions since these BAPI's are to be called from remote systems. So there is no 'where used' for this.
So to determine this will be very very hard. A long shot, not even sure this will work:
1. Determine BAPI's called from IDoc's.
2. Determine function module which is called from within BAPI.
3. Simulate the 'where used' functionality in other programs.
4. Check if any of these programs have a transaction code attached to it.
As I said, very hard, if not impossible.
BTW: Are you looking for BAPI's or BADI's? Big difference.
Edited by: Micky Oestreich on Mar 6, 2009 6:22 PM

FM for outbound payment idoc

Hi,
How do we find out the FM for outbound payment idoc?.Here are the details
Message type-PAYEXT
Idoc type-PEXR2002
Thanks,

This thread is was last replied more than a year ago, but I'll add a little just to contribute.
WE60 documentation for the IDocs don't really give much except field / segment
information, but don't talk about where the fields come from.
FI_EDI_PAYEXT_PEXR2001_OUT seems to be the right FM, not sure how it relates to IDoc type pexr2002 as 2001 is the older version, but perhaps it handles the difference somewhere inside.
As to where certain segment fields come from (i.e. the mapping to master data fields...) , I've been debugging and still in progress.
I have not been able to find any straight forward mapping, and my comments at the moment are:
For any particular segment field of PEXR2002, take a look at FM :
FI_EDI_PAYEXT_PEXR2001_OUT
to see how it populates the field. Chances are, the values come from the tables REGUH/REGUP/REGUV.
The payment run process as far as my knowledge is concerned is as follows:
1) Payroll Run -> Stores to table BT
2) Pre DME (e.g. trx PC00_M08_CDTA) picks data frm BT and creates payment data in REGUH / REGUP / and REGUV tables. This gives you an identification feature ID for the next step.
3) RFFOEDI2 changes status field in REGUH for particular payment data record based on ID from step 2.. this enables it to be picked up in the next step.
4) RFFOEDI1 converts the record in REGUH into an IDoc which can be processed in BD87.
I have debugged from step 4 backwards to step 3, i.e. I know that segment field X comes from REGUH field Y. Now I have to debug step 2 to find out how it populates REGUH field Y. If this comes directly from master data, then that makes life easier. But if this REGUH field Y comes from table BT of step 1, then perhaps I have to debug the payroll run somewhere. (Nightmare?
Anyway, if anyone knows better, please advise.

How to create an extension for generated type idoc

Hi all,
Can u please look into this
How to create an extension for generated type idoc ? for example Idoc type BATMAS02

Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
- Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
- Click on Create new and enter a description and press enter.
- Click on ZIDOCTYPE01 and then on the Create icon.
- Enter ZIDOCTYPE as the segment type, click on Segment Editor.
- Enter a description for your segment type and create.
- Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
- Save and generate, press back
- To release the segment choose Goto, Release from the menu.
- Check the box on the line of your segment.
- Save, back and enter.
- Your Idoc type structure should be displayed with your new segment.
- Save and back.
- To release the Idoc type choose Extras, Release type from the menu and Yes.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
regards,
srinivas

Desing requriment for processing the IDOC in real time

hi Gurus,
we have a requirement to design for processing the IDOC in real time i.e.all the IDOC must be store and process for give time line with out using BPPM tool.we have suggested to use cache storage or storing the files in file adapter.
please suggested good process with out compromising the Performance of PI.
regards
shankar

hi Raj,
Please find the example below for your reference
let say
System A-->PI--
>system B
system A sends multiple files based on time(daily or weekly) and real time( as an when the record created) to systerm B (CRM) in the form of IDOC Via. PI
we needs to club the real time files and send it to system B.How best we can do without using BPM.
regards
shankar

How to search for a certain cross reference using its name in FM 11?

How to search for a certain cross reference using its name in FM 11?

Well, thank you. I am only using Find dialog box. By "name", I'd like to give an example. The background is FM 11 structured. I have an element "xref" which is used to make cross reference. Now In Chapter 1, there is a sentence like "This is an ODU for ...". I made a cross ref of the word "ODU" to its full name "outdoor unit" in Chapter 2 (in the same book). After this, the word "ODU" in the sentence in Chapter 1 will no longer be a plain text. So I no longer can use the find dialog box to search for "ODU" because it is already an xref rather than text. I am not if it's clear.

Find Sales order number from IDOC number

I have a bunch of SO idocs, in status 64. They are then posted and Sales orders are created.
How can I programatically find the Sales order Number from the Sales Order idoc number once it is in status 53 (other than going to EDIDS and checking if status = '53' and grabbing the 'STAPA2' field there ).

Look at table EDIDS for sales order idocs and you can see SO number in any of STAPA1/2/3/4 variable for specific message id and message number.

Find out if a certain Stored Procedure runs

Hi all,
i have to state that i dont have much oracle specific database knowledge but i've spend half a day now gathering information about a certain problem and didnt find any really working solution.
What i want is to be able to find out if a certain stored procedure is currently running (executing) in the database. I need that to be able to prevent a user of my client application from executing a certain procedure more than once in the same time.
I have found some interesting information about the oracle Call Stack (dbms_utility.format_call_stack) but its not as helpfull as i orginaly thought because as far as i can see it only shows which procedures where executed (and are still executing) while the procedure with the dbms_output.put_line(dbms_utility.format_call_stack) command is executing.
But it doesnt show anything about procedures which are running in another instance of SQL*Plus, for example.
I have no other idea at the moment ...
So i hoped anybody in here maybe has an idea or maybe allready a solution.
But ... thanx in anyway =).
With greetings from germany,
Oliver Bankel

I'm sure there are several solutions.
This is how we solve this problem, not elegant but it works.
We have a table of procs that are running.
Active_Jobs
JOBNAME    VARCHAR2(35)
USERNAME   VARCHAR2(30)
STATUS     VARCHAR2(20)
Then within the proc
job_conflict               EXCEPTION;
BEGIN
select count(1) into v_status from ACTIVE_JOBS
where username = USER and status = 1 ;
if v_status > 1 then
   RAISE JOB_CONFLICT ;
end if;
INSERT INTO ACTIVE_JOBS (JOBNAME, USERNAME, STATUS)
   VALUES ('PROC NAME', USER, 1) ;
COMMIT;
DELETE FROM ACTIVE JOBS WHERE JOBNAME = 'PROC NAME' AND USERNAME = USER ;
COMMIT;
exception
   WHEN job_conflict THEN
     raise_application_error( -20010,'YOUR MESSAGE HERE');
END;

Procedure to find mandatory field in an IDoc Segment

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

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

XI and IDOC-Adapter / Restriction to certain IDOC Types?

Hi all!
We have some problems in trying to enable our XI systems for using our central user administration. The reason for that is that the "USERCLONE", ... IDOCs sent to XI by the CUA system are not processed normally in the ALE Layer but XI tries to process it through it's IDOC Adapter hence wants to route the IDOCs through the Integration Engine.
Is there a way to define the IDOC-Types to be processed by the IDOC-Adapter and to exclude certain IDOC types such that those are processed via standard ALE?
Many thanks in advance for any input you can give ...
Andy

Hi all!
For those who are interested - we have found the solution for this problem using some debugging
There is an "excemption table" where you can define required IDOC Types that should be processed via the normal ALE layer (instead of routing it through the IE).
To maintain the table entries you have to use report
"IDX_SELECT_IDOCTYP_WITHOUT_IS".
However - if you want to get rid of entries already made
with this report just have a look at note "790175"
Best regards,
Andy

Finding workitem for a certain idoc

Similar Messages

Maybe you are looking for