Problem regarding HRMD_A IDoc as outbound posting

Hi,
I have a requirement to post the data for HIRING (PA40 - hiring action) as IDOC, for which i am using HRMD_A.
Client's specific requirement is to Post the data, as soon as the user completes with the hiring of the employee through PA40.
I tried to add the logic in the Save of the Infotype, but which infotype is the last screen, how we can confirm, because all the Infotypes are not compulsory, he may skip the screen.
How to trigger the IDoc creation....
Can anyone help to find the triggering point for the same or any other alternative.
Basically client dont want to schedule a job that would take care of the posting at particular decided time and neither for Change Pointers....
Is there any work around for the same?
Any suggestions would be of great help.

Set change pointer active for HRMD_A, turn direct processing on in the partner profile, schedule a job every n minutes to create idocs from change pointers. And choose the correct forum for this, cause this has nothing to do with abap.

Similar Messages

Problem in HRMD_A Idocs: Object is Locked

Hi Everyone,
I would like to ask for assistance on the problem below.
We've encountered almost everyday failed HRMD_A idocs. Almost all of the idocs have the same error message: "Object is Locked. A locked key has been set for the object."
The object type is "P".
Can you help us on how to solve this problem?
Thanks in advance!

Hi,
For the locked object the sender system itself will not send the idoc.
and hence the error for the lock object might have been seen in the sender system and not the receiver system.
Yes you can process the idocs which are in error in the receiver system by frequently scheduling reports like
RBDMANI2-Schedule update of idocs with errors and
RBDAPP01- for ready for transfer idocs
I suggest you use the bapi way of transferring data, where the receiving system reads data from the sender system once a day and reads only that data which is changed during that date.
Regards,
Divya

ALE HRMD_A Idocs in status 52

HRMD_A Idocs in target system are not completely posted, turning into status '52'. Most of the times the infotype 1001 idoc with relationship P->S arrives before the idoc which has the actual objects(P, S) causing 'Relationship imposible because the object does not exist".
We use program RBDAPP01 for inbound processing of Idoc which should take care of Serialization based on the time stamp of idoc creation in source system.
Change pointors for Message type HRMD_A are processed using program RBDMIDOC in source system.
It is unlikely that relationship P->S is created without object P being created in the source system. So the change pointors should create the idocs in the same sequence. But it is not happening. Any body experinced similar problem?
Any help on this appreciated.

The question here is if all necessary data has been already transferred to target system . If data is selected based on change pointer than only data that has changed in source system is send to target.
Example: imagine you have change employee position using one of already created positions in the system. Change pointer will take than only the new assignment between employee and positions. It will not actually transfer the existing position it-self. In this case you must be sure that all existing positions are already transferred to target system.
In your example only new relationship between P->S is transfered to target. Employee data should already been there. The change here is not about creating new employee but only about the new relationship P->S.
Best Regards,
Andrzej

Problem in sendinfg Idoc's

Hi All,
I am facing problem in sending idoc's form one SAP sys to another. I had written a outbound program for sending IDOC's. When i execute the program the idoc is generated in the sending system ( With status 03 ) but no idocs were posted on the target system. But if i manually try to send the IDOC ( WE19 ) the idocs are posted to the target system.
Can any one give me an idea where the exact problem lies in...
Regards,
Swamy Mantha.

Hi,
Ru close the master idoc with a commit .
*Reward points
Regards

Standard IDOCS, Programs for posting FI & bank related data.

Hi,
(1)Are there any idocs available for posting FI documents, Vendor master?
(2)Are there any outbound idocs, programs for sending data to banks. EG:positive pay etc?
Kindly reply to these questions. Correct answer will be awarded points.
Regards,
Akshaya.

Hi,
There is message type BANK_CREATE for posting the FI related Bank details. Using the change pointers you can trigger the idocs for posting the bank related data.
Regards,
Uday

Custom status message in ALE HRMD_A IDOC

Hi,
We are using HRMD_A idoc for integrating two SAP systems. We want a custom check to be included in the ALE outbound processing, where for example if a field of an infotype is some value then we want to stop the IDOC from being transferred to the target SAP system. IDOC should stop with a custom error message in the status record. Is this possible using any of the user exits?
Thanks in advance,
Shravan

Requirement looks bit strange to me, if at all the IDoc is not needed to be sent for error message then why to Generate them, just filter out creation of IDocs by setting the Filters in Distribution model.
For your requirements you may want to take a look at Badi HRALE00OUTBOUND_IDOC.
Regards
Shital

Problem with HRMD_A06 idoc

Dear All,
I am using the IDOC HRMD_A06 for carrying out various operation on the available HR infotypes.Kindly go thru the below mentioned details for further insight of the problem
1.Scenario:
a.An interface to SAP HR system needs to be built
b.The interface will supply incremental master-data in
form of flat-files
c.An integration broker ,SAP XI will then convert the
flat-files to I-Docs and send I-Docs to SAP HR system
d.The I-Doc chosen for this purpose is HRMD_A.HRMD_A06
e.However this I-Doc is not supporting different
operations on incremental data like modify, delete etc
f.Further validations are also not being supported
g.Also segments for certain info-type records are missing
Example for Delete Operation mode:
Operation Delete: Delete existing infotype record
Expected Result: Only the particular info-type record, as supplied in the I-Doc should be deleted and not the entire personal number with all the info-types
Actual Result: The entire personal Number is deleted.
Is it that the Idoc behaves in this fashion or there is some other flag apart from OPERATION, which needs to be set.
Regards
Vinay

Hi Vinay,
Have you found a solution ?
Because I'm a similar problem by using IDoc HRMD_A06. I have not a segment E1P0021 when I delete the infotype 0021 on an employee. I have only its segment E1PITYP.
Regards
Mickael

REG: Error in IDoc adapter outbound processing

Hi All,
      I had a couple of doubts regarding these IDoc's.
1)        I am dealing with the web services to IDoc Scenario. When i am activated my wed services it               is giving an error like
"IDOC_ADAPTER.ATTRIBUTE_BE_NOT_SUPP" and "Only asynchronous processing supported for IDoc adapter outbound processing"
Can any one help me to Solve my Problem
2) How to find out whether the IDoc is of synchronous or Asynchronous mode
    and how to handle the synchronous type of IDoc's
Thanks in advance.
with Regards,
Kalyan Dannapaneni.

Hi Kalyan,
IDOCs are only Aynchronous (EO or EOIO).
If you want to call Synchronious, you will have to find remote enabled function modules (RFCs, BAPIs).
Or you have to use the ccBPM Synch-Async pattern to have an synchronos call passed to an IDoc, waiting for the Acknowledgement. In your situation I would check if a similar BAPI/RFC exists on your Backend SAP system.
Best regards,
Silvia

HRMD_A IDoc in error not raising an event

I have workflows enabled for IDocs in error.
If an inbound order IDoc (ORDERS) arrives in status 51, it triggers a workflow.
If an HR master data IDoc (message type HRMD_A) arrives in status 51, no workflow is triggered.
Here is what I have checked:
Partner profile has me as responsible agent in both cases.
Both type linkages are active for IDOCHRMD and IDOCORDERS event InputErrorOccurred.
Both IDocs types are posted in with the test tool and end up in status 51.
When I investigate the event trace, I can see that an event is raised for the ORDERS IDoc but not for the HRMD_A IDoc.
There are no errors in the type linkage status column.
So why would it be that the event is not being raised for the HRMD_A IDoc?
How can I find out what should be raising the event? I guess that there is a function module call to SWE_EVENT_CREATE or SAP_WAPI_CREATE_EVENT.
Kind Regards,
Tony.

Hi Tony,
I am a complete novice to workflow but I have a requirement liek yours to trigger workflow for idocs in error, so I was hoping you could point me in the direction of some documentation/steps on how to do this?

HRMD_A idocs sent and processed, but Org chart doesn't reflect it sometimes

From our HR box, we send HRMD_A idocs to our FI box - We have an intermittent issue where we have a position change & the idoc gets created & sent over.
On the inbound side, the idoc gets posted successfully with Status 53. However, this EE does not appear in the org chart as it does on the HR side.
We have these IDocs set up to process immediately, so it passes to the FI port and is processed all within a few seconds.
We come across this issue once about every 3-4 weeks and I can't seem to get anywhere trying to resolve it.
any ideas?

There are two main annoying problems with Flash Builder and swc's:
1. Flash Builder doesn't reflect changes made to swc files
Solution : First of all - keep your swc files inside your project folder, you can also disable global swc cache: change as3api.cpp code,refresh swc in flashBuilder bug!
2. Flash Builder breakes content inside swc files (and also popular problem "TypeError: Error #1034: Type Coercion failed: cannot convert flash.display::MovieClip@1f21adc1 to...")
Solution : locate the project .actionScriptProperties file and set useFlashSDK=”false” : Flash Builder 4.7 – useFlashSDK | In Flagrante Delicto!
In this case you can also download latest Apache Flex SDK to target new Flash player versions: http://flex.apache.org/
Hope this helps!
P.

Problem with Delivery IDOC staus 51

Hi all,
I have problem with Delivery IDOC.
An IDOC is sent from the logistics provider with reference to a manually created delivery, which creates another IDOC & another partial delivery.
The second IDOC created then confirms the partial delivery created by the first IDOC.
When IDOC try to confirm this delivery, it goes to status 51 with error " Delivery does not exist".
In some case IDOC was correctly processed & confirmed the delivery.
In some cases it went wrong.
Any ideas regarding this?

Hi Suneel,
It seems there is timing issue between the first IDoc and second IDoc.
When the first IDoc has not yet commit to DB then the second IDoc tries to process with reference to the first IDoc.
Is there any that can distinguish between 1st and 2nd IDocs?
In other word, can you post the second IDoc within minutes delay?
Just my two cents.
Regards,
Ferry Lianto

Possible to trigger HRMD_A IDoc immediately

Hi experts,
Can you please let me know if it is possible to trigger an Outbound HRMD_A IDoc immediately i.e. as soon as someone creates a new record for any of the infotypes associated with this IDoc the IDoc is sent; without having to schedule PFAL or BD21.
Thanks and regards,
Brendon

Can you please let me know if it is possible to trigger an Outbound HRMD_A IDoc
immediately i.e. as soon as someone creates a new record for any of the infotypes
associated with this IDoc the IDoc is sent; without having to schedule PFAL or BD21.
Well I think some confusion out here, PFAL or BD21 does not have any control on when the IDOC
is sent they will just read the infotype data and create IDOCs. WE20 Partner Config has got the
setting to tell system whether COLLECT the IDOCs in ready state or dispatch as soon as they
gets creates (PFAL/WE21) Without scheduling BD21/ PFAL you will not have IDOCs itself
triggering comes later.
Hope this clarifies.

To control the frequency of Idocs to be posted in SAP

Hi,
Our scenario is from flat file to Idoc,When Idoc is getting posted,it is invoking BAPI.
Idocs are getting posted frequently.
In our case whts is happening,when one Idoc is posted,The BAPI will be locked by that Idoc,when 2,3 and 4th,etc.Idocs will come then those Idocs are failing as BAPI is locked by the first Idoc.Is there any way in XI with which we can control the posting of Idocs in SAP,So that all the Idocs will be getting posted successfully and BAPI will not be locked when the 2,3 and 4th,etc. will come?
Best Regards,
Harleen Kaur Chadha

Hi !
By definition the incoming IDOCs in ECC should go to a queue, to avoid blocking calls and make an asynchronous scenario. Then ECC will process each IDOC of the queue when the resources are available.
Maybe I just don't understand how this BAPI is affecting the idocs that come after the first one with problems. What are the problem syntoms? any error message? XI should be able to send all IDOCs to ECC without failing and then ECC should process them in without affecting XI.
If you go to tn BD87 in ECC, what are the statuses of the IDOCs?
Are you using a standard IDOC ? is your BAPI stateless?
Regards,
Matias.
Edited by: Matias Denker on Jan 7, 2008 11:51 AM

Regarding ALE/Idocs PDFs & complete Documentation & Step by Step Procedure

Hi Gurus,
Iam working on Netweaver XI and i need some PDF's on ALE/Idocs.
1. How to create and send a custom idoc?
2. Serialization of idocs?
3. Archiving of idocs?
4. Idoc Acknowledgement?
5. How to send multiple Idocs at a time?
6. Idoc Sheduling?
7. Idoc bundling and Packaging?
8. How to Debug a Idoc?
For the above questions i need complete procedure and Pdf's upon these and send me some FAQ's on them.can any one send me the details plz very urgent.plz send Especially pdf's. My id is ajaykodali22 at the rate of gmail.com
Thanks & Regards,
ajay kodali.

Hi,
Data Creation in Idoc
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.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction 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 it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
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
Create Message Type
Go to transaction 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
Go to transaction 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
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
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://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
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://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
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://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
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://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND 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.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Regards,
Shiva.

Problem regarding installation of drivers of hp m1005 mfp on windows 8.1(64 bit)

i am facing problem regarding the installation of the drivers on my new windows 8.1 pc.
i have already downloaded the full solution present on the website twice but found my efforts in vain.

Hello @naga_akkireddi , and welcome to the HP Forums.
I am sorry, but to get your issue more exposure I would suggest posting it in the commercial forums since this is a commercial product. You can do this at HP Commercial LaserJet Forums.
I hope this helps!
Please click “Accept as Solution " if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks" for helping!
Jamieson
I work on behalf of HP
"Remember, I'm pulling for you, we're all in this together!" - Red Green.

Problem regarding HRMD_A IDoc as outbound posting

Similar Messages

Maybe you are looking for