Find UserExit from IDoc Type

Dear all,
here I have a IDCO Type ACC_GOODS_MOVEMENT02
Is there any one who can tell me the UserExit of it?
How can I find generelly UserExits from IDoc typ?

Hi,
Enhancement: ACBAPI01 & Exit: EXIT_SAPLACC4_001.
We can find the exits by searching in inbound function modules.
Reddy

Similar Messages

How to find out the idoc type required for our requirement

Hi,
How to find out the list of available idoc type in SAP. It will be good if i get to know the table name where all the idoc type definitions are gets stored.
Say i have some requirement and for that requirement how i can find the proper idoc type to be used. (assume functional consultant is not providing that information)
Points will be given for the useful answers
Thanks,
Prasanna

Hi prasanna,
we can get SAP idoc types in tcode we31.For every requirment there will be different message type.
For example we want idoc type for account invoice receipt.
First find out message type for that purpose which can be found in we81-ACC_INVOICE_RECEIPT.
Get this message type and search in we82 where we can find message type and idoc type linkage.
try this way.
Reward if it is usful.
Thanks,
Srikanth.A

Sales Order Creation from IDOC type ORDERS05

Hi experts,
   I have tried to create sales order using IDOC, using FM input IDOC_INPUT_ORDERS. But when I include segment E1EDP05 - IDOC: Document Item Conditions. I got the following errors "Conditions in IDoc E1EDP05 transferred: Check data", with status 51, and application is post.
   Fields I filled in the segment:
KSCHL
KRATE
UPRBS
MEAUN
Thanks.

SAP Xpert friends,
I really need help in figuring out this error I get when I send an IDoc from external system to SAP.
Here is what I do....
create empty idoc of type ORDERS01
idoc.MESTYP = "ORDERS";
idoc.SNDPRN = "1171";
idoc.SNDPRT = "KU";
idoc.MANDT = "400";
idoc.SNDPFC = "AG";
idoc.MESCOD = " ";
idoc.MESFCT = " ";
idoc.TEST = " ";
create segment of type E1EDK01
add field MENGE with a value
add segment e1edp01 to idoc
create segment of type E1EDP19
add field QUALF with a value to segment
add field IDTNR with a value to segment
add segment E1EDP19 to idoc
send idoc
When I check WE02 in SAP, I can see the idoc, but
get this error
Here are all the STATUS RECORDS
<b>50 IDoc added
64 IDoc ready to be transferred to application
62 IDoc passed to application
51 Error: Application document not posted
    <i>VKORG, VTWEG, SPART cannot be determined</i>
    for customer 0000001171 , vendor</b>
I checked on Internet and found that VOE2 can be used to setup ... this is what I have in VOE2
Customer    Vendor SOrg     DChl   Dv
1171        0000001171       1000   00
Thanks for help...

IDOC types required for SAP FI

Hi All,
How to find the various IDOC types/messages types available for total SAP FI module.My client wants to generate interfaces to get the data from legacy into SAP and from SAP to legacy.I think Client provides only description of the interface like Vendor Account posting and Customer payment so I want all the IDOC types/Message types that are related to SAP FI.
I have the below interfaces :
Accounts Posting : (AP)
1)Vendor Mastre update - FK01
2)AP open items to be Paid - FB60 - VENDOR INVOICES
3)Open Items that were Paid in SAP - VENDOR PAYMENTS
4)Postive Pay EDI feed - > EDI - Bank Payments to Vendor for a Company Code
5)AP Rapid Mart
6)Positive Pay Feedback file -> EDI - Bank Statement for Payment to Vendors for Company Code
Accounts Receivable : (AR)
1)Customer Master Update - XD01
2)Sales Invoice Batch - Sales Invoices - FB70
3)Credit, Debit & Adjustments, Receipts -> AR Debit / Credit Memo - FB70
4)Dunning Letters feed -> AR Dunning Letters FOR A Company Code
5)Customer Statements -> AR Customer Statements - FOR A CompaNY CODE
6)lock BOX PAYMENTS ->EDI - AR Customer Lock Box payments
7)Quarterly Charge Off -> AR Credit Memos - FB70
GENERAL LEDGER : (GL)
1)TZG Journal Entries (GL XFR) -> GL entries - FB50
2)Hyperion feed -> GL Balances to Hyperion
3)ADP Payroll feed -> GL Transactions - FB50 - ADP -> SAP feed
4)PowerTrack freight expense -> EDI - GL enries - FB50
Please help me out and your help will be appreciated.
Thanks,
Ramesh.

Hope this helps:
http://help.sap.com/erp2005_ehp_03/helpdata/EN/db/8d6b46163f11d2893a0000e8216438/frameset.htm
http://www.erpgenie.com/sapedi/message_types.htm
http://www.erpgenie.com/sapedi/message_types_bp_ac.htm
http://www.erpgenie.com/sapedi/message_types_bp_lo.htm
Regards,
David

Create Idoc Type under ECC6

Hi folks,
I've created a new Idoc segment for an existing idoc (The original idoc doesn't have the fields I need). I'm now trying to create a new Idoc type taking into consideration the new Idoc Extension I've created. When I type my new idoc type and select 'basic type', I believe I should get prompted (somewhere) to enter the Basic Idoc type and Extension type, but when I create a new basic type, I don't get the option to add my new extension. And If I copy the original basic type, I don't get my new segments.
Can someone please tell me what I'm missing in the create new Idoc Process?
Cheers,
Steve

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

Find Idoc extension type for Basic Idoc type

Hi all,
Is there any way to find existing extesions for Idoc given by SAP? For example, for basic idoc DEBMAS05 for version 4.7 , Idoc extension is DEBMASEXT.
In similar way I want to know what is Idoc extension for Idoc basic type PREQCR02 [Create Purchase Requisition].
Thanks in advance.
Madhura

The reason is preqcr02 is a generated idoc type and matmas05 and debmas05 are not generated idoc types .
You can search in table EDBAS for this . If you go for dynamic debuggin , message comes from form
create_ext_structure in include MSED5F02
data: l_edbas type edbas.
select single * from edbas into l_edbas
     where idoctyp eq edi_iapi01-idoctyp.
if l_edbas-generated eq 'X'.
   message e099(b1) with
      'Action is not possible for generated idoctypes'.
endif.
Edited by: anil sasidharan on Feb 25, 2009 12:51 PM
Edited by: anil sasidharan on Feb 25, 2009 12:59 PM

What is the IDOC type for changing PO price in ECC from SNC?

We have configured the consensus finding tolerance check for date and it is working. When we create confirmation from PO worklist by changing the price and the delivery date, it goes for manual approval if the date change is outside tolerance. Once the confirmation is approved by the buyer we are getting two Idocs in SAP. One is ORDRSP-ORDERS05. This one has the new price, but does not change the price in the PO. It only creates confirmation. The other one is PORDCH-PORDCH02. This one does not have the new price. It only changes the delivery date in the PO line item. We want one single IDOC which will change price (if price is changed), change delivery date and create confirmation. is that possible? If yes, what IDOC type would that be?
Thanks for your help.
Soumen

Hi Soumen
Can you please check whether the below settings are available on ERP side
SPRO-MATERIAL MANAGEMENT-PURCHASING-CONFIRMATIONS-SET UP CONFIRMATION CONTROL
select your confiramtion control line
lets say ZICH, select the confirmation sequence on left hand side
for your order acknowledgement,XX
check the field "Price"
and give the allowed tolerance values in fileds
Permitted Price Overrun in % (Inbound EDI/SOA)
Permitted Price Shortfall in % (Inbound EDI/SOA)
Now resend the data.... it will work
ORDRSP-ORDERS05 should work this time
Best Regards
Vinod

Find program for an IDOC type

Hello Gurus,
I need to identify what program or transaction does a Particular IDOC type is associated to.
How do I find Program related to IDOC type?
How many ways to find such link?
Regards,
Abhishek.

Hello Gurus,
My scenario is to find the easiest way to search for the Link between and IDOC type (Outbound idoc) to a program.
I have list of all the IDOC type now I need to find from where these IDOC´s are triggering from?
Regards,
Abhishek...

Not able to find the field xmwst in the idoc type fidccp02

Hi all,
I am developing abap program which uploads values from a flat file and creating an idoc.
the basic idoc type is fidccp02, in this idoc i am not able to find the fiels xmwst - automatic tax calculation , if anyone give alternative soluations it will be appreciated.
thanks in advance
a.fahrudeen

I guess if standard IDOC doesnt have that field, then you need to extend the IDOC. YOu need to find user exit in that IDOC and write the code.
--Archana

Which iDOC Type for Credit/Debit notes generated from SD Module ?

Hi,
We are implementing an EDI Solution for SD Invoices which would involve sending EDIFACT Messages generated out of mapping the SAP iDOC TYPE INVOIC02 to the EDIFACT fields.
We also have to send Credit and Debit Notes generated from SAP in the SD Module in the same path. We are currently planning on using INVOIC02 for doing this.
My Question: Is this the proper approach ? We don't want to use the Credit / Debit advises in FI-GL to post to Credits to Customer Account.
Is there any other iDOC Type or message type that we should be using for SD Credit/Debit Notes ?

Hi Mahesh,
Thank you for your help.
In my client location data is posted non-sap to sap through SAP XI/PI.
so i need to tell the xi guy to which IDOC is used for this interface and technical names.
Can you help me.

Is it Possible to import an IDoc type from R/3 into APO system

Hi Gurus ,
Could you please guide if we can import an IDoc type from R/3 system to APO system ?? If yes , can you please give the guidelines / step - by - step procedure for this.
Thanks in advance ,
Roseline

hi
yes u can export an idoc from r/3 to a legacy system.
the brief outline is as follows:
1. set up an rfc connection. it has to be 'T' type in t-code sm59
configure the saprfc.ini file if on windows based os. if on unix based os configure rfcexec.c to have the login details of apo system.
2.set up logical systems( at least 1 each for r/3 and apo) using T-code SALE.
3.assign clients to the logical sytems using T-code SALE..
4.create ports using tcode we20.
5. create idoc segments using we30 and release.
6. create idoc type using we31.
7. create message type using we81.
8. assign message to idoc using we82.
9.build a customer model using tcode bd64.
10. create an outbound process code usint tcode we41.
it will help if you specify your idoc that you want to use- for vendor, customer and material there are predefined distributions and idocs.
Thanks.

ALEREQ idoc type from PI system

Hi,
I have to change the vendor data from Inbound idoc which will be coming from PI system.
but, to get the inbound idoc for vendor we have idoc type as CREMAS05 and message type as CREFET
But,at PI side to send the vendor data, they see the idoc type as ALEREQ01 for message type as CREFET.
Kindly provide me the resolution.
Thanks in Advance.

hi
yes u can export an idoc from r/3 to a legacy system.
the brief outline is as follows:
1. set up an rfc connection. it has to be 'T' type in t-code sm59
configure the saprfc.ini file if on windows based os. if on unix based os configure rfcexec.c to have the login details of apo system.
2.set up logical systems( at least 1 each for r/3 and apo) using T-code SALE.
3.assign clients to the logical sytems using T-code SALE..
4.create ports using tcode we20.
5. create idoc segments using we30 and release.
6. create idoc type using we31.
7. create message type using we81.
8. assign message to idoc using we82.
9.build a customer model using tcode bd64.
10. create an outbound process code usint tcode we41.
it will help if you specify your idoc that you want to use- for vendor, customer and material there are predefined distributions and idocs.
Thanks.

Creating IDoc Type from Change Pointers using RBDMIDOC

Hi All,
we are executing program RBDMIDOC(Creating IDoc Type from Change Pointers) evrey 15 minuts in background.
Issue : if some jobs are taking more than 15 minuts then next jobs are failed,
is next job will pick up any idocs that were missed?
there is no extesion's and ther is no Z-fields are used in that message type , we are used OILMAT as mesage type.
Regards,
DSK
Edited by: suresh dameruppula on Aug 5, 2008 2:04 PM

Hi,
Include a step in your job and have a program which checks if a job is already running. If yes do not start the next instance of the same job.
in the custom program just call function module
   CALL FUNCTION 'ZBC_JOB_ALREADY_RUNNING'
      EXPORTING
         JOBNAME           = p_job
      IMPORTING
         JOB_RUNNING       = w_count
      EXCEPTIONS
         JOB_NOT_SPECIFIED = 1
         OTHERS            = 2.
Code within FM ->
   select count(*)
   into   job_running
   from   tbtco
   where jobname = jobname
   and    status = 'R'.
where p_job is the job name.
w_count is current running job count. If its greater than 1, then stop the 2nd with an error message.
Rgds,
Hema

Find Tcode from given userexit & Badi

Hi Experts,
i got a requirement to find Tcode from the given userexit and badi, Can anyone help me to find the Tcode .
Note: I know how to find the userexits & Badi from the Tcode.
Please help me to find the Tcode from the given userexit.
Thanks in advance.

Hi,
If you know the exit name; then goto table MODSAP and get the enhancement for the same.
Then go to SMOD and get the package name...based on the package name, got to se80 and get the transaction name from the object hierarachy...
Sometimes you may have the enhancement name in the program name(enhancementname)
Hope this helps you
Regards
sk

Userexit in idoc

Hi Friends,
I have one extension idoc type requirement, now i want to insert the code in userexit. how can i find the user exit related to the idoc.

Hi,
can u explen what is your Scenario, here i am given some userexit for idoc.
u can find it from SMOD
MWMIDO01
MWMIDO02
MWMIDO03
MWMIDO04
MWMIDO07
MWMIDO08
MWMIDO09
MWMIDO10
MWMIDO11
MWMIDO12
MWMIDO13
SIDOC001
SIDOC002
EX......
MWMIDO01 (User Exit)
With this user exit, the contents and structure of IDOC WMTOID01
'Transfer order' can be influenced customer-specifically in the outbox.
Call transaction and other important requirements
The user exit is performed in the function module that sets up IDOC
WMTOID01. This is done after the IDOC setup but before it is transferre
to the ALE interface. The standard function module for setting up IDOC
WMTOID01 is called L_IDOC_CREATE_WMTOID01. The IDOC setup is part of th
transfer order generation. This means that the source code can run both
asynchronously in the update program and online. For this reason, all
error messages must be issued as abend messages to guarantee a correct
termination with rollback. Furthermore, you must not use any key words
such as COMMIT WORK, ROLLBACK WORK, LEAVE, or the like.
Parameters and options
The user exit in the program is function module EXIT_SAPLLIDO_001. In
order to be able to use the user exit, you must create Include ZXLIDU01 and activate the enhancement with transaction CMOD. As parameters, you
can use the transfer order and IDOC data:
o   TO header (import parameter I_LTAK)
o   TO items (table parameter T_LTAP)
o   Control record of the IDOC that has been set up (import parameter
     X_IDOC_CONTROL)
o   Data records of the IDOC that has been set up (table parameter
     T_IDOC_DATA)
This user exit can basically be used to:
o   change or redetermine the data in IDOC WMTOID01 that were determined
     during the standard procedure or provide partners with additional
     information using empty fields of this IDOC.
o   change or enhance the data for controlling the IDOC processing in
     the control record of the IDOC.
o   If you enhanced the basic IDOC WMTOID01 with your own segments, you
      have to fill these segments including the necessary data.
The user exit returns the modified IDOC data to the calling program by
means of the following parameters:
o   Control record of the IDOC that has been set up (export parameter
      X_IDOC_CONTROL)
o   Data records of the IDOC that has been set up (table parameter
      T_IDOC_DATA)
The modified IDOC is passed on by the calling program to the ALE
interface for sending.
Although changes to table T_LTAP are without any meaning, they should
still not be made.
Examples
Below, you will find some conceivable changes including the necessary
source code.
o   You want to send additional data on TO item level. These data are
      transferred in the standard segment of IDOC WMTOID01.
      With field 'Goods recipient', information is transferred whether the
      external system should additionally print accompanying documents for
      the sent transfer order. The indicator for printout from the TO
      header and the printer from the TO items are specified in this
      field.
      In addition, a separate description is written into the field
      'Unloading point'.
INCLUDE ZXLIDU01
      tables: e1ltori,
       loop at t_idoc_data.
*........Zusatzinfos aus dem Transportauftrag..........................
     if t_idoc_data-segnam = 'E1LTORI'.
        move t_idoc_data-sdata to e1ltori.
        loop at t_ltap
         where tanum eq i_ltak-tanum
           and tapos eq e1ltori-tapos.
          exit.
        endloop.
        if sy-subrc eq 0.
          move i_ltak-drukz to e1ltori-wempf.
          move t_ltap-ldest to e1ltori-wempf+2.
          move e1ltori to t_idoc_data-sdata.
          modify t_idoc_data.
        endif.
*........Zusatzinfos die individuell beschafft werden..................
        move 'USER-EXIT' to e1ltori-ablad.
        move e1ltori to t_idoc_data-sdata.
        modify t_idoc_data.
     endif.
    endloop.
o   The IDOCs that have been set up are to be transferred to the
     external system via two different logical destinations, depending on
     the transport type. This requires two different partner profiles.
     The partner profile depends on the message type, message variant and
     message function. Message function 'EIN' is used for stock
     placements whereas 'RES' is used for all other movements. You have
     to maintain the partner profile for these two message functions
     'EIN' and 'RES' as well.
INCLUDE ZXLIDU01
   if i_ltak-trart eq 'E'.
     move 'EIN' to x_idoc_control-mesfct.
   else.
     move 'RES' to x_idoc_control-mesfct.
   endif.
For transfer orders on deliveries, the external system requires
additional delivery data such as name of the goods recipient, route,
shipping point, and the like. In this case, the large amount of
additional data can only be transferred via an additional IDOC
segment. That is, you have to define a seprate IDOC type that
consists of the basic IDOC type WMTOID01 and a separate enhancement
type. In the enhancement type, you define the new segment, for
example Z1LTORZ, that refers to the standard segment E1LTORH. Filling the data of the new segment can be done as follows.
INCLUDE ZXLIDU01
      tables: e1ltori,
              z1ltorz,
              edidd,
              likp.
      data: flg_neues_segment.
      data: begin of xidoc_data occurs 0.
             include structure edidd.
      data: end   of xidoc_data.
*....>>> Neues Segment anlegen Z1LTORZ <<<.............................
*........Bestehendes IDOC sichern......................................
loop at t_idoc_data.
    move t_idoc_data to xidoc_data.
    append xidoc_data.
endloop.
*........Neuen IDOC-Typ und Erweiterungs-Typ im Kontrolsatz fortschr...
move:
       'ZZWMTOID' to x_idoc_control-doctyp,
       'ZWMTOID1' to x_idoc_control-cimtyp.
*........Aus dem bestehenden IDOC ein neues IDOC erstellen.............
       dabei wird das neue Segment aufgebaut und eingebettet
refresh t_idoc_data.
loop at xidoc_data.
*........Merken:neues Segment soll nach dem Segment E1LTORH kommen.....
       if xidoc_data-segnam = 'E1LTORH'.
         flg_neues_segment = 'X'.
       endif.
   *........Standard-Segmente übernehmen..................................
       move xidoc_data to t_idoc_data.
       append t_idoc_data.
   *........Neues Segment übernehmen......................................
       if flg_neues_segment eq 'X'.
   *........Lesen Lieferung und Daten in neues Segment übergeben..........
         if not i_ltak-vbeln is initial.
           select single * from likp
            where vbeln eq i_ltak-vbeln.
           if sy-subrc eq 0.
             clear t_idoc_data.
             move-corresponding likp to z1ltorz.
   *........Neues Segment sichern.........................................
             move 'Z1LTORZ' to t_idoc_data-segnam.
             move z1ltorz to t_idoc_data-sdata.
             append t_idoc_data.
           endif.
         endif.
       endif.
       move space to flg_neues_segment.
     endloop.
if it is help full to u please give max rewad point.

Find UserExit from IDoc Type

Similar Messages

Maybe you are looking for