IDOC type related to Payroll and Employees Attendance and Absence

Hi Evrybody,
Right now im working on ALE INBOUND Interface, which relates to transfer of data.
I'm searching for an Basic IDOC type related to Payroll and Employees Attendance and Absence,
If any pointers would be much helpful.
Thanks n Regards.
[email protected]

Solved myself.

Similar Messages

IDOC Type for Tcode CC01 and CC02 (Create / Change Change Numbers)

We are trying to integrate Change Master from a 3rd party system to SAP R/3 4.72.What is the IDOC Type for Tcode CC01 and CC02 (Create / Change Change Numbers)

Thanks...
We have looked at this IDOC Type. However we are not very sure how the components (Material/BOM etc.) will be mapped into E1AEEFM segment in the IDOC.

IDoc type for post Chargeback and RTV (Return to Vendor) in OTC (SD)?

Hi EDI Folks,
Can anyone tell me which IDoc type (Logical Message Type) should be used to post Chargebacks and RTVs (Return-to-Vendor) in standard Order-to-Cash method.
PS : The Customer is sending Chargebacks/RTVs in 812 X12.
Thanks,
Creasy

Thanks vijay,
Basically I am not an PI guy, I wanted to know what can be the best possible sceniario to communicate from sap to PI in my case,
Thanks,
Mahadev

For Inventory Adjustment : Which Idoc type to be used and why?

Hi Gurus,
For Goods Movement in one of the MM-Purch Implementation I used the Idoc type : MBGMCR03
at that time inventaory was not playing a big role.
But for now for doing inventory adjustment (Inventory has importance now) which Idoc type to be followed:
Can I use same Idoc type : MBGMCR03
Or Shd I go for Idoc type : WMMBID02
In some threads I read if MM you shd. go for MBGMCR03 and for IM : WMMBID02.
But why I dont know the answer...
Please give me your views on this.
Thanks
Amresh

MBGMCR03 is basically the BDBG idoc type and uses BAPI_GOODSMVT_CREATE to post the goods movement... You can check the documentation for the FM /BAPI to determine what kind of goods movement is possible. You can look at T158G table to find the t-codes supported. If you can post your inventory adjustment using the BAPI, you can use MBGMCR03, as long as middle ware can support that format...
As far as the WMMBID02, It uses the IDOC FM (which in turn also uses the MB_CREATE_GOODS_MOVEMENT)..

Basic idoc type for asset creatioon and asset acquisition

Hi
Please can anybody tell me the basic IDOC type provided by SAP for
- Asset creation
- Asset acquisition.
Thanx in advance....

Hi,
Go through this link
http://www.sap-basis-abap.com/fico/configuration-in-asset-accounting.htm
help.sap.com/bestpractices/BBLibrary/documentation/B44_BB_ConfigGuide_EN_Nordics.doc
Reward points if found helpful...
Cheers,
Chandra Sekhar.

Related to payroll and company code

Dear Guru's
I want to know the Company code of a PERNR in the PAYROLL
means from where can I get the Company code of a PERNR
means from which structure ..
Thanks in Advance '
Regards,
PAVAN.

Hi Pavan,
Pl refer to my regarding payroll on the ABAP forum.
Regards,
Suresh Datti

Implementation of IDOC types FINSTA01 and PEXR2002

Hi All,
I want to implement the 2 IDOC types PEXR2002 and FINSTA01 using EDI.The requirement is like I have to generate both the inbound and outbound processing for both the IDOC types using EDI.
I have the following queries :
1)What are the basic fields that are required for both the inbound and outbound processing(like file format)
2)How the inbound and outbound processing will be triggered like how can I send the file from SAP to EDI or how can I get the file from EDI to SAP and how to uplaod the record into SAP is there any SAP standard transactions or any standard reports or do I have to configure in the SPRO etc.
3)What are the settings that I have to configure?
Please help me out and your help will be appreciated.
Thanks and Regards,
Ramesh.

Hello Ramesh,
The answers to your questions are a few chapters in some books, meaning its quite large.
But in short.
1. the minimum fields are what is required by that particular transaction in SAP for inbound and for outbound you gotta check with the receiving party what they need.
example , if you are posting a PO in SAP, then what are the mandatory fields, thats the minimum.
With every idoc , incoming, there are a few ways to post, most common is via function modules.
Lets say you know a partner which will communicate via EDI, you have to maintain a partner profile in WE20.
There you define the incoming and outgoing messages.
Every message has, idoc type.
Transactions WE42 and WE43 are where you define a process code for attaching the message type/idoc type to a Funtion module.
Also there is config for setting up output types, see transaction NACE.
This is a process with lots of parameters.
You would be better off getting a book which explains it all in a proper order.

Idocs, idoc types, tables

can anybody tell me   what type of idoc types are typically used in a regular order to cash cycle in sd .
and   are there   tables related to it?
what is the tcode to see them
n.bhardwaj
my id is
[email protected]

Dear Neha,
Idoc Types:
ORDERS01     Purchasing/Sales
ORDERS02     Purchasing/Sales
ORDERS03     Purchasing/Sales
ORDERS04     Purchasing/Sales
ORDERS05     Purchasing/Sales
INVCON01     Stock change data for inventory controlling
INVCON02     Stock Change Data for Inventory Controlling
INVOIC01     Invoice/Billing document
INVOIC02     Invoice/Billing document
INV_ID01     Invoice
DELFOR01     Delivery schedule/JIT schedule
DELFOR02     Delivery Schedule/JIT Schedule
DELIVERYPROCESSING_EXECUTE01     Delivery processing
DELVRY01     Delivery interface
DELVRY02     Delivery interface with dangerous goods data
DELVRY03     Delivery interface
DELVRY04     Delivery interface
You can view Idoc types in transaction WE30.
WE02/WE05 for displaying IDOCs.
WE19 for testing IDOCs.
ALE and IDOC:
ALE stands for Application Link Enabling and is used for distribution of data. IDOC is an Intermediate Document. It carries the application data from one server to another server.It uses the RFC(Remote Function call) .
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
It is the the combination of Segements.
Segment : All the required fields will get assigned in relavant segement.Like that we will have lot of segments.We will assign all the segments to IDOC type.In the required level(Parent & child level .Like tree nodes).
Idocs Type is a Structure by lot of segments.
IDOC is generared at the time of run time .
It will have the data.
There are basically two types of IDOCs.
Basic IDOCs : Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs : Extending the functionality by adding more segments to existing Basic IDOCs.
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sap-img.com/
http://www.sappoint.com/abap.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
Need info on automatic determination of tax code at PO
Hope this will help.
Regards,
Naveen.

Multiple message types for an idoc type

Hi all,
I created one custom idoc type with six segments. I heard that one idoc type can have any number of message types
if it is so pls tell me how to assign these two message types for my idoc .
i want to create multiple message types because i want to send same idoc type to diff legacy systems.
My requirement is message type one is only for first three segments and message type two is for another three segments .
The outbound program 1 for mess type 1 should fill fill the data for only first three segments and second outbound program corresponding to mess type 2 should fill the data for last three segments
how should i design for my requirement. suppose if the idoc has two message types then it has two outbound programs?

Hi Kunal,
Below are my thoughts from a design perspective,
My requirement is message type one is only for first three segments and message type two is for another three segments .
The outbound program 1 for mess type 1 should fill fill the data for only first three segments and second outbound program corresponding to mess type 2 should fill the data for last three segments
Before you look upon the no. of message types you need, i guess you need to look at the business requirement. Per your requirement you want to send send two sub sets of data. The first subset in the first 3 segments and other three segments for the second subset of data.
Is the structure of the first subset of data similar to the second subset If not, better to create two IDOC Types. If they are similar, then create one IDOC Type with three segments and have two message types for each subset of data.
For Ex: ORDERS05 is the IDOC type for Orders, this IDOC type provides capability to carry data related to any type of orders
but the action on the data is facilitated by the message type like ORDERS for create, ORDCHG for change, ORDRSP for Order response etc.
OR
Are these two subsets of data related to each other, if yes understand the relation? If not related at all then you might be better of creating two separate IDOC Types.
Like in the above example A purchase order is related to a sales order so you can use the same IDOC type, but in case of a order response and ASN that data sent is different and hence you will need different IDOC types (even though a SO is related to a DN).
how should i design for my requirement. suppose if the idoc has two message types then it has two outbound programs?
The above again depends on the how tightly/loosely coupled are the data sets, you can have just one program and have a simple case statement on the message types or have two different programs.
You will also have to consider points like, if any of the subsets is more prone to more change in terms of the structure and associated business logic. If yes, then you might want to keep the programs separate to reduce work on regression testing etc.
I am sure you will receive more inputs from the experts on the forum and the list of points to look for will get longer , so understand the requirement, dependencies and if you have any specific questions you could post it on the forum.
Regards,
Chen

Hi gurus what is basic IDOC type

hi gurus what is basic IDOC type

Basic Type:
Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.
Segments:
Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.
Steps in creating Segments:
T.Code WE31
Enter the name for your segment type and click on the create icon.
Type the Short text.
Enter the variable names and data elements.
Save and Go back.
Go to Edit -> Set Release.
Repeat the steps to create more segments.
IDOC TYPE:
Business data is exchanged with an external system using the IDoc Interface.
IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.
Steps in creating IDoc Type:
T.Code WE30 to create IDoc Type.
Enter the Object Name, Select Basic Type and click Create Icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDoc name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press enter
The system transfers the name of the segment type to the IDoc editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation.
Save it and go back.
Go to Edit -> Set Release.
Message Type:
Steps in Creating Message Type:
T.Code WE81.
change the details from Display mode to Change mode
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
Assign Message Type to IDoc Type:
T.Code WE82
Change the details from Display mode to change mode.
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
Reward Points if useful.

Mapping problem for IDOC Type DESADV

Dear all
I need to change Segment E1EDP07 in the message type DESADV.
I should concatenate VBELN and VGPOS into BSTNK.
I tried to do this with BD79 (Rules for Data Converting). This seems not to work as I can get only 1 sender Field.
So I tried to use the userexit EXIT_SAPLBD11_001, but it seems that this is not used. I have set a break-point for debugging and treated the IDOC with RSNAT00 without any stop.
Do you have any ideas how I can do this?
Herbert

>
Herbert Schlup wrote:
> I have 2 entries for my DWSADV01
>
> 1 with FM IDOC_INPUT_DESADV and the other with IDOC_INPUT_DESADV1
With the first one, you cannot do much, as there is no user exit in it. But in the second one, there is a user exit when the idoc data is parsed the exit name is EXIT_SAPLV55K_004 and is called in the subroutine DESADV_IDOC_PARSE in the function.
But please note that the function IDOC_INPUT_DESADV1 is used with process code DELS for message type DESADV and Idoc type DELVRY01 and IDOC_INPUT_DESADV is used with process code DESA and message type DESADV with IDoc type DESADV01. So you might be using IDOC_INPUT_DESADV function and unfortunately there are no user exits to handle your requirement.
My advice would be to check with the source system or the middleware to define the mapping of these fields according to your requirement. But if that is not possible, then you need to first check which message type and IDoc type you are receiving and proceed accordingly
KR,
Advait

Idoc types for Advanced Returns Management (ARM) in EHP4

Hi
Does anyone know the Idoc type/Message type for return sales order with Advanced Returns Management (ARM) in EPH4? I have searched all ORDERS Idoc types /associated function module and I am not able to find the new fields available in ARM in the function module. Your immediate feedback in this regard will be highly appreciable .
with regards,
Joseph Anand B

Hi,
In order to customize advanced returns, you have to do the following:
a. Define the return reason codes
b. Define the refund codes
c. Define the inspection code catalog
d. Define the order types that are relevant for advanced returns management
e. Define the logistical follow up activities
f. Define the number ranges for inspection sheets
g. Define the default values.
Follow the node under advanced returns management. Please let me know if you need any specific information. Refer to the guide for advanced returns management in the SDN papers.

INVOIC IDOC type sample

Hi,
Can someone provide me with a sample inbound INVOIC IDOC with planned delivery costs. We already use thei IDOC type for incoming invoices and are trying to enhance it to include planned delivery costs. I have tried using segment E1EDp05 to give the condition type and amount corresponding to planned delivery costs. But, the IDOC is always erroring with an imbalance between credits and debits and it does not seem to be passing the values from E1EDP05 segment to the invoice creation function module.
Any help will be greatly appreciated.
Thanks in advance
Regards
Chitra

Hi CA,
Just ty with this sample...
If you want to send invoices with delivery costs from you must use Transaction CMOD to program the EXIT_SAPLMRMH_014 user exit as follows:
Create a customer project and use Transaction CMOD to call it. Add the MRMH0002 enhancement and the EXIT_SAPLMRMH_014 component. Insert the source code into the ZXM08U25 include.
DATA: ls_data_s01 type E1EDS01,
lv_beznk type MRM_RBKPV-beznk.
IF I_IDOC_DATA-SEGNAM = 'E1EDS01'.
ls_data_s01 = I_IDOC_DATA-SDATA.
IF ls_data_s01-sumid = '020'.
lv_beznk = ls_data_s01-summe.
E_RBKPV-BEZNK = lv_beznk.
E_CHANGE = 'X'.
ENDIF.
ENDIF.
Regards,
Kumar

IM Movement types related to PP

Hi,
can some share with me the IM/WM Movement types related to PP and in which scenario we use that.
Thanks,
Chakku

Hello chakku,
Here is the list of all mvt type in Inventory management (WM mvt type is related to Inventory mvt type and configured in OMLR t-code)
http://help.sap.com/saphelp_46c/helpdata/en/fc/6cec6eb435d1118b3f0060b03ca329/frameset.htm
The main mvt types are as follow (Pl. see the scenario in above link)
101 - Receipt against production order (Final product receipt)
122 Return delivery to supplier or to production
261 Goods issue for an Production order
262 - Return/reversal from production order
521/523/525 Goods receipt without order
571/573/575 Goods receipt for assembly order
Hope this helps.
Regards,
Arif Mansuri
Reward if answer is helpful.

Notification IDOC Type INOTIF01 failing in poasting

Hi,
I have a program which extract data and post IDOC for notification of Type INOTIF01. The program was working fine in SAP 4.6C. As in ECC6.0, SAP has introduced an addition popup in IW32 transaction, thus my IDOC generation and posting program is failing while posting IDOC as it is not able to handle that new popup.
IT is using function module "IDOC_INBOUND_ASYNCHRONOUS" to process the IDOC data populated in Control and Data Tables.
Pls advice what i can do to handle this new popup which is causing problem and IDOC is failing.
thanks and all help is appreciated.
Sandy

Hi,
It is a custom program which is using IDOC Type INOTIF01 and Message TYpe INOTIF. It populate Data in IDOC CONTROL & IDOC Data internal tables.
After Populating data in internal tables, it uses "IDOC_INBOUND_ASYNCHRONOUS" function module to create and post IDOC.
I checked in EDIMSG table and for message Type INOTIF , IDOC Type INOTIF01 is linked and it has entries upto 46C version only. there is no entry in table for 700 version for message Type INOTIF.

IDOC type related to Payroll and Employees Attendance and Absence

Similar Messages

Maybe you are looking for