Mandatory fields for inbound - idoc HRMD_A07

Hi All,
I need to create an Employee master record in R/3 by triggering an idoc .
i came to know ,i can use "HRMD_A07" .
can any one help me giving the mandatory datas to trigger the HRMD_A07.
Thanks & Regards,
Arun

Hi,
PA objects exist if infotypes 0000, 0001, and 0003 have been created.
So fill the segment accordingly, but I am not sure whether you can directly create the employee from Idoc, you may have to take the Idoc option of LSMW.
Br/Manas

Similar Messages

Mandatory fields for inbound delivery idocs

hi all
i want to generate inbound idocs for inbound delivery ASN
i am using message type DESADV and idoc type /AFS/DELVRY03
in order to generate inbound idoc what are mandatory values i have to pass to the idocs
thanks
Anil

HI,
I created inbound idoc for ASN Inbound delivery in test mode we19
i got idoc with status 62, when i am trying to process the idoc in bd87, its allowing me
is there any other way to process the idocs , so that status will be 53
thanks

Mandatory Fields for IDOC ORDERS01 for Pricing Condition EDI1 to trigger

Hi ,
I'm Testing an Inbound ORDRSP using we 19 for Pricing Conditions EDI1. What are the Mandatory Fields for IDOC ORDERS01
Thanks

hello,
I think it's better to execute VA01 to create a sales order; in that way you should have an idea of mandatory fields.
Thanks.

Mandatory fields for mapping in ORDERS idoc.

Hi
I m working on File to idoc scenario for creation of sales order in ECC 6.0 , now I want to know what are the mandatory fields in ORDERS idoc which needs to be populated or else disbaled so that the sales order gets created properly in the ECC 6.0..
Pl let me know the method of finding mandatory field for mapping for any idoc and which fileds of idoc are to be disabled.
Pl help ..
ans will be rewarded .
thanks & rgds
mojib

HI,
U can disable the control record segment and in the IDOC adapter use the option apply control record from payload.
If you have set the Apply Control Record Values from Payload indicator in the receiver IDoc adapter, the following fields are filled from the IDoc-XML payload:
·        MESCOD
·        MESCFT
·        TEST
·        EXPRSS
·        STD
·        STDVRS
·        STDMES
·        SNDSAD
·        SNDLAD
·        RCVSAD
·        RCVLAD
·        REFINT
·        REFGRP
·        REFMES
·        STATUS
·        DIRECT
·        OUTMOD
·        CREDAT
·        CRETIM
read the information in below link:
http://help.sap.com/saphelp_nw70/helpdata/EN/ab/bdb13b00ae793be10000000a11402f/frameset.htm
thnx,
chirag

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.

FILE to IDOC SCENARIO NEED MANDATORY FIELDS IN MATMAS IDOC

Hi
I'm learning a scenario like File to Idoc which is i need some what are the mandatory fields for creting the message mapping.. between source file and MATMAS IDOC... because it was showing several fields.
is there any way to find out the fields we need to map compulsory... for sending IDOC successfully.
Thanks
Babu

Hi Babu !
Log into the R/3 system, transaction WE60, enter the idoc type MATMAS01 or 02, 03, 04, then press F8 or go to Documentation menu, HTML Format.
It will display a document, telling you which fields are optional and which mandatory.
Regards,
Matias
PS: please award points if helpful.

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).

Mandatory fields for BAPI_ACC_DOCUMENT_POST

Hi
I am getting the follwing data from the file (Which is coming from oracle) invoice number and the amount,
from that i have to use Fb70 tcode for posting ,Please help me what are the mandatory fields for FB70,
how will get those fields from SAP. How to use the BAPI ?
Regards
Pabs

hi
check out this thread
Re: BAPI_ACC_DOCUMENT_POST
hope this helps
regards
Aakash Banga

Mandatory fields for xd01

hai,
what are the mandatory fields to create the datas for xd01.(customer master data).
regards
surender

HI
MANDATORY FIELDS FOR CREATING CUSTOMER DATA ARE:
Account Group---ktokd(field name)
Name---Name1
Search term----sortl
postal code----pstlz
country-----land1.
Regards,
vineela

Can any one pls tell me the mandatory fields for BAPI_ACC_DOCUMENT_POST

hi all ,
Can any one pls tell me the mandatory fields for BAPI_ACC_DOCUMENT_POST
what all data i need to give to post a document.
Thanks and Regards
JK

Hi...
part of my source code:
** Header Data " Sending comp code
wa_documentheader-comp_code = 'XXXXX'.
wa_documentheader-doc_date = '20060620'.
wa_documentheader-pstng_date = '20060620'.
wa_documentheader-doc_type = 'XX'.
wa_documentheader-username = sy-uname.
wa_documentheader-ref_doc_no = 'XXxxxxxx'.
wa_documentheader-header_txt = 'Text Header.
wa_documentheader-bus_act = 'XXXX'.
*it_currencyamount
wa_currencyamount-itemno_acc = '1'.
wa_currencyamount-currency = 'COP'.
wa_currencyamount-amt_doccur = 1943.
APPEND wa_currencyamount TO it_currencyamount.
*it_accountpayable
wa_accountpayable-itemno_acc = '1'.
wa_accountpayable-gl_account = '1234567890'.
wa_accountpayable-bus_area = 'DIV'.
wa_accountpayable-item_text = 'Text 1 XXxxxxx '.
wa_accountpayable-pmnt_block = ''.
APPEND wa_accountpayable TO it_accountpayable.
*it_accountgl
wa_accountgl-itemno_acc = '2'.
wa_accountgl-gl_account = '1234567890'.
wa_accountgl-item_text = 'Text 2 XXxxxxx'.
wa_accountgl-bus_area = 'DIV'.
APPEND wa_accountgl TO it_accountgl.
wa_currencyamount-itemno_acc = '2'.
wa_currencyamount-currency = 'COP'.
wa_currencyamount-amt_doccur = ( 1943 ) * -1.
APPEND wa_currencyamount TO it_currencyamount.
CALL FUNCTION 'BAPI_ACC_DOCUMENT_CHECK'
EXPORTING
    documentheader = wa_documentheader
TABLES
    accountgl      = it_accountgl
    accountpayable = it_accountpayable
    currencyamount = it_currencyamount
    return         = it_return.
clear it_return.
CALL FUNCTION 'BAPI_ACC_DOCUMENT_POST'
      EXPORTING
        documentheader = wa_documentheader
      TABLES
        return         = it_return
        currencyamount = it_currencyamount "currencyamount
        accountpayable = it_accountpayable "accountpayable
        accountgl      = it_accountgl "accountgl
      EXCEPTIONS
        OTHERS         = 01.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.

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.

Inbound IDoc(HRMD_A07) problem in delimiting the infotype records

Hi All,
I am using Inbound IDoc (HRMD_A07) approach to update infotypes. I found that I am able to create a record in an infotype, but there is a problem in delimiting the infotype.
Please help me out in case I am missing something.
Thanks,
ABAP_DEV

Hi,
Did you get this resolved. Even i'm facing this issue. Is it a config or do we have to do something in the IDOC.
Thanks,
Jilly

Mandatory fields for vendor master load

Hi Experts,
what are the mandatory fields for the vendor master upload? how can I find that?
Thanks for the help.

In addition, you can also refer the links:
http://www.auditnet.org/docs/SAPR3AccountsPayable.txt
http://users.ev1.net/~gmorris/securitydocs/SAPR3AccountsPayableMatrix.doc
Hope thisll give you idea!!
<b>P.S award the points.!!! !!!</b>
Good luck
Thanks
Saquib Khan
"Some are wise and some are otherwise"

PS: Setting Project Profile as a mandatory field for Project Definition

Hi,
I would like to know how to set Project Profile as a mandatory field for Project Definition (CJ20N or CJ01). I tried to look for controls at OPUK config but the Project Profile is not available for definition - either mandatory, optional, suppressed, etc. Would appreciate if you can share your expertise on this.
Thanks!
Regards,
Vivian

Hi,
I would like to know how to include some additonal fields in OPUK/OPUJ. We have defined some .INCLUDE component / fields to SAP standard table PRPS/PROJ. We want those fields to also appear in OPUK/OPUJ so that we could also defined their characteristics - whether input, mandatory, suppressed, etc.
Thanks!
Regards,
Vivian

Mandatory Field for Entering Delayed Reason for project during scheduling .

Hi Friends
Here I have a question on "Scheduling"?
My Client want an mandatory field for entering the delay reason if any phase or tasks or project definition get delayed.
Your input would be highly appreciated
Regards,
YAGHAG

Hi Abhijit,
Thanks for your prompt reply.
I am implementing cprojects 4.5 in PLM 7.0 and not in PPM 5.0.
Regards

Mandatory fields for inbound - idoc HRMD_A07

Similar Messages

Maybe you are looking for