ALE using HRMDA message type - Comit not perform in receiving system

Hi,
I want to use ALE to transfer HR master data between two ECC instances. I have set-up all the configuration; distribution profile, filter etc... I tried to transfer the master data using standard SAP report RHALEINI.
The iDoc is generated and transfer correctly in the receiving system. The final status of the iDoc is 53 - Application document posted. The issue we have is that the comit to tables is not happening. Infotypes remains empty even if the status of the iDoc says it was posted. We are trying to transfer infotype 0000, 0002, 0001 and 0006
Anyone can help ?....
Thanks
Louis

Hi Ted,
Thanks for your answer,
Autorization is the first thing that we consider. We generate the IDOC by the program RBDMIDOC .
The job's user is the sap_all authorization. So it should not related with auth.
And this does not always occur. For example, two days ago it occurs, but today does not occur.
Best Regards
Hasan.

Similar Messages

IDoc Message Type different in sending to receiver system

Hi,
I am sending DESADV (message type) IDoc to other SAP system. But problem is in other system Message Type DESADV is available in a different name ie DESADV1.
No of segments and their name are same in both the system are same..
In that case if i am sending DESADV from sending system whether receiver system can get IDoc?
Note: In sending system i could not able create message type DESADV1
Sa_R.

Hii..
Looking like Strange scenario...
Normally we must have the Same message type in both Sender and Receiver systems.
Bcoz whenever the IDOC is Received in the Receiving system it will process based on the Message type. So the Same message type must exist in the Sender as well as Receiver.
I can think of a Solution: Just try..
In the Sender system Create a Reduced message type (Tcode BD53) Of the Message type DESADV. Select all the Segments and Fields
In the Receiver system also Create a Reduced message type with the Same name as Sender system (Tcode BD53) Of the Message type DESADV1. Select all the Segments and Fields.
Then use this Reduced message type since it exists in both the Systems.
<b>Reward if Helpful.</b>

Tcode to send custom data using custom message type in ALE

I have ceated custom message type and i want to send data to say system B.I wanted to know Tcode to send custom data using custom message type in ALE.
for example:
material data...message type = matmas....tcode = BD10.
like this.
i hope you have got my question.
plz guide me?
regards
mallikarjun mangalore

Hi,
Sending data through ALE is not a single-step process. Take a look at http://www.sapgenie.com/ale/. The paper at http://www.sapgenie.com/sapgenie/docs/ale_whitepaper.doc is a wonderful resource for the ALE process.
Regards

Received unexpected message type does not match expected type

1.Two Biztalk Applications A,B one for sending the request(A) and other application will send the response to A.
2.I have two schema Request and Response in Aplication A which i have exposed as webservice.
3. Application B share the same response schema .
I am using WSBasicHTTP sysnchronous ports to send and receive the message.
WHen Application B send the response , i get the error "unexpected message type does not match expected type "
but i dont know why i get such error when the schemas are share by both application. Please advice
Regards
Suresh

Hi Suresh,
Whenever you are doing request-response like calling web service etc, i would suggest to use Passthrough pipeline while sending and use XML receive for receiving the message.
Because when you are sending the message out it doesn't needs any promoted properties so you can use Passthrough this will avoid extra Assembling/Validation etc tasks performed by XMLSend pipeline.
But when you are receiving response that time it expects MessageType property to be promoted because normally you will have receive shape configured to some Typed Schema. So you will have to use XML Receive pipeline.
Thanks,
Prashant
Please mark this post accordingly if it answers your query or is helpful.

ALE Distribution for Message Type FIDCC2

Dear all,
I would like to confirm my steps below in setting up the ALE distribution of message type FIDCC2, to ensure that I did not do anyhting that impact other company code that already live in the system :-
1. Use tcode OB87 to add the Global Company Code, XBJ01.
2. Use tcode OBV7 to link a dummy (non-existence in sending system)
Chart of Account to the Global Company code XBJ01.
3. Use tcode OBB5 to assign the Global Company Code, XBJ01, setup in step 1. to the an existing company code BJ01.
4. Use tcode BD64 to setup a distribution with message type FIDCC2, and
filter with value XBJ01.
5. Create an FI document using tcode FB01 with company code BJ01.
6. IDOC is created successfully with message type FIDCC2.
Is there above steps correct? As there are times I receive an error message when trying to do a PGI with company code other than BJ01 "F1302 No cross-system company code is defined for company code TR01".
Another question is, with setting up of FIDCC2 with ALE distribution, any transaction in SAP that will generate a FI document will have IDOC created, right?
Thank you.
Best Regards
Chee Hean

I don't know if you still have this problem but my team and I faced a similar issue in production. Due to a project we're handling, a tool that we are executing requested us to create a Distribution Model based on FIDCC2. This stuck hundreds of thousands of FI Document. Actually, for any FI document the system generated an FIDCC2 and it's not possible to reuse those IDocs because the FIDCC2 Message Type has a structure completely different from FIDCMT (the original message that the system should generate). We identified all the IDoc that should be generated and re-create the Idocs in the target system and the Idocs we posted correctly. We change the FIDCC2 IDocs status to 62 or 32 (depending if inbound system or outbound system). I recommend to investigate about this message type before use it. This Message Type is stronger than any other message type so it must be filter perfectly otherwise, for sure, problems will appear.
Regards,
Hugo

Activate change point for message type - message type FIDCC1 not in list

I want to set up idoc for sending entire FI documents.
For this I want to use the change points in the message type FIDCC1 but this message type is not in the list of transaction BD50 (neither if I go via SALE)
I'm not allowed to add it myself, I get a warning the name is not in the namespace (Zxxx or Yxxx).
Is there a way I can add this message type in this list?
-> change points are generally activated
-> ECC 600
edit: I see the message type is in WD81
Edited by: Renaat Vanhaverbeke on Apr 28, 2010 11:05 AM

I found the solution: when I tried to add the message type in BD50 I got the warning the name does not match the namespace rules. But by opening the Performance Assistant I could start the transacion RDDKOR54 to display the namespace rules.
By exiting this transaction I got the question if I want to bypass the namespace check and by answering positive on this I could save the new entry.
PS: I also found that alle message types are defined in table EDMSG

How to add custom infotype in ALE for HRMD_A message type

Hi Friends-
Pls help me for our req we are using HRMD_A Message Type for HR master data but now we need to add one custom infotype ( 9902 ) also in standard ALE filters for this message type how i can do that pls let me know ?
<<removed_by_moderator>>
Regards
Meeta & Glory
Edited by: Vijay Babu Dudla on Dec 14, 2008 11:38 PM

Hi
Thanks for your support,
Pls let me know which steps i should go ? my secanrio is inbound side only,
step 1 ) Define idoc extension for HRMD_A01 using WE30 transaction and define it in partner profiles
step 2) do i need to write some code in BADI also to update information for my custom infotype also if yes then where and which BADI pls let me know ? because already am working on one badi HRALE00INBOUND_IDOC for few validation for incoming data.
step 3 ) add this new custom infotype in my standard ALE filters.
Pls let me know if am mistaking some where or if i have to do some thing else ?
Regards
Meeta & Glory

Error handling using fault message type in outbound synchronous ABAP proxy

Hi,
We've a scenario, outbound synchronous ABAP proxy to synchronous SOAP receiver. The requirement is to send multiple records in a single rquest and get response for all the records sent (in the same response message).
Say if I send 10 records from ECC, I should get 10 records as response from SOAP to ECC. But the problem here is, there could be some invalid requests, for which an invalid error status code should be sent as part of response.
Source Structure
Req_Proxy
    req (0..unbounded, string)
Response Structure
Resp_SOAP
Resp (0..Unbounded)
       respString (0..1, String) (carries the actaul response message)
      status code (0..1, String) (carries the status of the response, for ex, 001 (successful), 002 (error))
And now we are planning to make use of Fault Message Type, to track the errors from SOAP (status code 002). But, we are not sure on how to track this for all the requested records. Is it possible to track the errors for all the requested records in a singe call using fault message type? For eg if 8 records are successful and 2 are invalid, then we should get 10 records in response 8 for valid and 2 for invalid accordingly.
Please calrify.
Thanks.
Rohit

For eg if 8 records are successful and 2 are invalid, then we should get 10 records in response 8
for valid and 2 for invalid accordingly.
Check if you can modify the WSDL structure to include an error node that would get populated incase of invalid entries....this would mean that you get the success and failure details in the single message....also at the proxy-end make the necessary change in your DT.....may be then you do not need to use the fault message...
Regards,
Abhishek.

How to use PO message type to output 'Form' as PDF file

Dear experts,
I am working for a topic of how to use PO message type to output 'Form' as 'PDF file', and save to external file system automatically.
Any one familiar to this topic, please kindly give me some guide, thank you!
Regards,
Joyce

Hi,
Go through the program RSTXPDFT4 (Converting SAPscript (OTF) or ABAP List Spool Job to PDF), you will get some idea. Using this program you can convert spool into PDF file.
-Alpesh

Trip type does not exist in the system (T702G)

Hi,
In HR - Module - Travel Management.
I am trying to create a travel request for an employee.
i am getting the error message :
Statutory trip type does not exist in the system (T702G)
how to assign the trip type to a particular employee.
regards
sam

If you are applying as employee you need to configure trip schema and single field control for webdynpro provided you are using webdynpro application as employee.
there in the tri provision variant you need to enter the variant you have created.
Under that select the travel planning trip schema PL.
on right hand side you have a field trip schema: statutory where you need to select appropriate schema from drop-down.

Document of this type is not supported in your system

Hi All,
Scenario : Through SBWP we are trying to send an attachment ( PDF/XLS/WORD ) in email.
Issue : When we try to attach any document/file, we get error - Document of this type is not supported by your system administration. We checked the TSOPE table and it didn't have PDF entry and XLS/Word were blocked. However our other system had same entries but we could attach documents and send email without any issues. Could anyone please shed light on it?
Thanks in Advance.

Hello Rahul,
Hope you are doing well, have you checked TSOPFAV table ?
Also, check the following link, you may get some ideas
Sending Mails - Home Page - ABAP Development - SCN Wiki
Regards,
Siddhesh

RFC not created in receiver system

Hi,
FIile-rfc received in receiver system until yesterday.now the RFC not reaching to receiver system.They are no changes and no change in RFC structure.
all the ques are clear and RFC connectin to the receiver system is alo fine and CC monitoring is also green and in the audit log everything is sucessful.sxmb?moni messages are sucessful.
please let me know where i can check ...
Regards,
hyma

Did you see any logs in receiver RFC channel?
Check the receiver service for interface in moni- SOAP header-Main document.
Also check if any conditions are specified in receiver determination.

Message type is not populating in the Inbound idoc control record

Hi,
I have created an Inbound Idoc function module and have done the necessary Idoc settings. But, while testing in WE19, I observed that control record is not getting populated with message type and it is dumping.
The settings which I have done in WEDI as follows:
1. Created Idoc segments with necessary fields and released
2. Created Idoc type for the segment type
3. Created message type
4. Assigned message type to basic type
5. In the inbound processing settings,
filled the ALE attributes with the Idoc function module name and input value '0'
6. Assigned FM to basic type and message type
7. Created process code and assigned the process code to message type
Please let me know, the reason for the message type not populating in the control record. Useful answers will be surely rewarded.
Best Regards,
Mallika

Hi,
Maintain partner profile (Transaction code WE20) for the message type you defined in WE81 and put your process code in partner profile and check your logical system settings also in transaction SALE.
Thanks
Rahul

IDOC message type WMMBXY not including Serial numbers in GR material documents when created with reference to an Inbound delivery

Hello,
We currently have an inbound ALE process (message type WMMBXY and basic type WMMBID02) to post GR's against inbound delivery. If the inbound delivery item is maintained with serial numbers, we want those serial numbers to be pulled into the goods movement material document (and stored in SER03).
Currently segment E1MBXYJ is maintained with the inbound delivery number in field VLIEF_AVIS and Inbound delivery item number in field
VBELP_AVIS. In segment E1MBXYI, no purchase order is assigned and the fields EBELN and EBELP are blank. The movement indicator (KZBEW) has the value 'B'.
Even after making the above settings, the serial number(s) maintained on the Inbound delivery item do not get saved to the material document.I did look at OSS note 833603 (Solution for 2 - GR for Inbound delivery) and we have followed the same settings. This works when there is no serial number in the Inbound delivery. However if we have serial numbers, the IDOC posts successfully, however the material documents in MB03 do not have any serial numbers copied over from the Inbound delivery where the serial numbers are definitely assigned.
Any help you can provide is greatly appreciated!
Thanks,
Ashvin
P.S
If we manually create the GR via MIGO, the serial numbers are automatically applied to the GR material document. This is what we want to accomplish via the above IDoc process.

Hi
Try with enhancement MWMIDO08. See note 833603 - EDI: Goods receipt for stock transport order for further information.
I hope this helps you
Regards
Eduardo

Output Message Type MAHN not getting picked up in PO

Hello Experts
   I have configured customized output type ZMAH (similar to MAHN) for reminder process. When I am creating PO this output type is not getting picked up automatically. If I am maintaining it manually I am able to send message for ME9F (Purchase Order) and ME91F (Reminder) successfully. Upon deremination analysis I am getting this message 502 " Output ignored (requirement 103 not fulfilled) ". Reminder are getting picked up from Purchase Value Key to PO.
Any help is appreciated.
Thanks
Ankit

Hello Tej
I have maintained output device but same result.
Here I am listing all parameters that I have used for configuration can anyone please take a look and let me know if I am missing anything
Steps for new Message Type for PO Reminder (ZMAH)
1.     Defined new Table 026 Purchasing Output Determination: Document Type
                                                    (ii) 027 Purchasing Output Determination: Purch. Org./Vendor for EDI
2.     Defined new access sequence Z515 Access Sequence for Archiving.
Following are parameters to the Access Sequence
Access Sequence Number = 1
Table = 026
Description = Purchasing Output Determination: Document Type
Requirement = 103
Exclusive = Yes (box checked)
Access Sequence Number = 2
Table = 027
Description = Purchasing Output Determination: Purch. Org./Vendor for EDI
Requirement = 103
Exclusive = Yes (box checked)
3.     Maintain Output Type ZMAH for PO
General Data
Access Sequence = Z515
Access to condition (Checked)
Multiple Issuing (Checked)
Change Output
Program = SAPFM06P
FORM Routine = ENTRY_NEU
Replacement of Text Symbol
Program = SAPMM06E
FORM Routine = TEXT_SYMBOL_REPLACE
Default Values
Dispatch Time = Send Immediately (when saving application)
Transmission Medium = External Send
Communication Strategy = 0001 (E-mail Document)
Processing Routines
Transmission Medium = 5 (External Send)
Program = SAPFM06P
Form Routine = ENTRY_NEU
Form = MEDRUCK
Partner Roles
Medium = External Send
Funct = VN
Name = Vendor
4.     Fine-Tuned Control: Purchase Order
Oprat. = 3
CType = ZMAH
Name = Output for Reminder
Short Text = Urging letter (expediter)/reminder
Update Print Related Data = Yes (checked)
5.     Maintain Message Determination Schema: Purchase Order
Procedure RMBEF1 (Purchase Order)
Step = 101
Cntr = 3
CTyp = ZMAH
Description = Output for Reminder
Requirement = 103
6.     Assign Schema to Purchase Order
Procedure RMBEF1
7.     Define Partner Roles for Purchase Order
Out. = ZMAH
Med = 5 (External Send)
Funct = VN
Name = Output for Reminder
Name = Vendor
8.     Test Condition Maintained in MN04 (Master Data)
Purch. Org. = 0001
Vendor = 101281
Partner Funct = VN
Medium = 5 (External Send)
Date/Time = 4 Send immediately (when saving application)
Output Device = LP01
Cover Page Text = Reminder PO number &EKKO-EBELN&
Also I have configured Purchasing Value Key, reminders are coming to PO correctly.
Thanks
Ankit

ALE using HRMDA message type - Comit not perform in receiving system

Similar Messages

Maybe you are looking for