ALE-IDocs: Issue on COGRP1 & COGRP6 Message Types

Dear Experts,
I need to send the Cost center groups data and Profit Center groups data from one system to other, I had sent this for one time using the tcodes, from now on I need to send only the changed data, so configured the ALE for this.
I activated change pointers generally in BD61 and then activated change pointers for message types in BD50. Cost Center Group (COGRP1), Profit Center Group (COGRP6).
Why is RBDMIDOC program not showing any output when executed with standard message types COGRP1 and COGRP6 ?
It is working fine with other message types like MATMAS, DEBMAS, COSMAS, PRCMAS, CREMAS.
Tcode: BD59: Assignment of Object Type to Message
Tcode: WE30: Develop IDoc Types
Tcode: BD52: Change document items for message type
So, COGRP1 does not have assignment of all the segments that are displayed for the IDoc Type: COGRP01 in WE30. Do we need to assign all these segments and fields to the message type in BD59? If so, how to create this ALE Object Types and what are these table names and fields in BD52., any user exits kind of thing for populating the fields if we do this way?
I am really having trouble and great confusion with this.
I would really appreciate you if you could provide me an answer or a hint.
Thanks in advance for the time you spent on this.
RV

Hi,
You need to follow following steps for the activation of change pointer.
1) Enable change pointer globally (BD61)
2) Enable Change Pointers for a Message Type (BD50)
3) Specify the Fields for Which Change Pointers Are to Be Written (BD52).
BD59 is used to Assign Filter Object Type to IDoc Field. Then you can add filter while creating distribution model.This is used when you have to filter the Idoc at distribution stage. It has nothing to do with the change pointer technique.
In BD52 , you have to assign the change pointer object(this you can find using T.code SCDO), table name and field.In your case change doc object is ALESETS
Just make sure that you are making changes in Cost center groups data and Profit Center groups and then execute program RBDMIDOC.
Regards,
Monika

Similar Messages

IDOC:inbound scenario for posting Message type ORDRSP

Hi All,
I am doing a inbound scenraio to post message type ORDRSP.
Acknowledgement gets created in Purchase order successfully but texts at header level and item level are not getting updated in the purchase order
I am using the segment E1EDKT1 and E1EDKT2 for header texts . For item texts I am using the segments E1EDPT1 and E1EDPT2.
Any pointers to this is appreciable.
Thanks in advance.

Hi,
Depending on whether the Order is a third party order are not, the texts are picked up from either SO or PO.
Put a break point on line 842 in the Include LEINMF11 and debug, this should help you get to the root cause of the issue.
Regards,
Chen

IDOC Segment missing for MATMASS Message type

Through change pointer program for the message type YAUIHUBMATMAS IDOC is triggered.
1) Change pointers are defined in system for the message type T Code u2013 BD52.
2) If respective field is changed in material master , this data is stored in change pointers table BDCP.
3) Background jobs are scheduled every day, which searches for the changes pointer table and triggers the idoc.
In our case IDOC is getting generated but with one segment missing.
We have analysed the succesful and failed IDOC and found desrepency is field updation of BDCP table.
Succesful case contain material number in object value of ZZMDST field where as failed contain some other value.
Can anyone please help us to guide how the BDCP table is updated and the values are mapped in it or any other suggestion to find why the segment is missing in it.
Regards,
Roshni.

Jürgen L. wrote:
> I have never seen a YAUIHUBMATMAS IDOC, nor a ZZMDST field .
> This seems to be home made.
>
> You are expecting that standard SAP programs are generating change pointers for your z-fields?
> Do you see a change history in material master for your z-field?
>
>
> follow the slution from this thread:
>
Yes ,This is a Z -field.
Change pointer is triggering the idoc fo this Z-field but in some cases one segment is missing .
This is z-field in the basic data view of material master.
Yes , we have checked the change history in material master for this field it is getting updated there in BDCP table as well but in BDCP table if this field is flagged then object value is not contain material number instead it contain some other number .
But in case of succesful IDOC the object value is same as material number.
Regards,
Roshni

Idoc MBGMCR02 what is the message type

what is the message type for idoc MBGMCR02?

I guess my real question is where do i go to set up a new partner. I think it is SALE but then i am not quite sure what to do there.
I think i need to set up new partners for outbound and inbound processing. then i need to go into we20 and use the MBGMCR message type to be able to be exchanged.
Am i correct
and is there a place where it tells how to use transaction sale to set up new partners?

Sales order idoc error only on ORDCHG message type (ORDERS01)

Hi. I am adding segment E1EDK04 to our sales order idocs in order to pass tax jurisdiction code to R3. When I create the order (message type ORDERS), I am extracting tax jurisdiction code from the idoc and I am adding it to the ship-to address screen via a BDC table within user exit include zxvedu04. The new order gets saved with the TXJCD, and this works fine.
I am now testing maintenance scenarios. For ORDCHG message types, I am inserting the TXJCD within user exit include ZXVDBU02. The idoc processor abends in 51 status with message:
"Control data in the IDoc E1EDK04 has been transferred. Check data".
If I walk the same status 51 idoc through BALE without changing anything, I see the TXJCD get posted to the order, and the order is saved correctly the second time.
Does this mean I need to add something additional to the idoc control data on an ORDCHG or something?
Thank you.
Brendan

I was not able to get any farther on this. It would seem that when the idoc is processed in the foreground, something is being populated that is not present when the idoc come across to R3...
The thing is, when I walk through the idoc in the forground, there are no errors that pop up. I can save the idoc after foreground processing and it moves into 53 status.
Thanks for any ideas that you might have on how to gather more infromation.

ALE-IDOC ISSUE(material getting locked for enhancement)

Dear all,
I have extended the idoc and enhanced inbound material master function module to suite the requirement .
The challenge is that the material is getting locked when the material sent from bd10 and prodction version view for which function module extended is not getting created.The error log says that "material is locked".But when the idoc is processed again from we19 the material is not getting locked and PV(production version is successfully created).
Can anybody guide me how this locking issue can be resolved?(have done unlock -lock before and after BDC for Production version).
Thanks.

Hi,
If some one using the same material in another session, definitely the idoc will fail as the material is locked... In order to overcome this first lock the material u want to send, if doing this u get foreign lock then u will know that already someone locked it , so once gain process the same record until the foreign lock is gone, once it is gone process ur record and then unlock the material.
Regards,
Nagaraj

Ale/idoc issue.

dear all,
i want to post the idoc for sinlge personal no.that means sinlge from sap hr client to other client.how to place the condition.how to trigger this idoc.

HI,
The T-code is PFAL(RHALEINI).
Thanks & Regards
Manas

ALE - error in custom message type creation

HAI friends,
I am new to ALE IDOC, i am creating custom message type for custom table . i created segment, idoc, message type and executed outbound program . in outbound client, status is dispatch ok. so problem in outbound.
my problem is in inbound . i created one function module idoc_input_zmsg. In test tool for idoc processing ie. TCODE WE19, i clicked my segment and then i clicked the inbound function module button . In function module text box my own function module idoc_input_zmsg is available. but when i click ok button, i am getting the following error.
"INTERFACE FOR FUNCTION IDOC_INPUT_ZMSG IS INCORRECT".
PLS HELP ME . THANKS IN ADVANCE.
WITH REGARDS,
SENTHIL KUMAR.R

All the IDOC processings FMs should have similar interface like this.
*" IMPORTING
*"     VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"     VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     VALUE(WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*"     VALUE(APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*"     VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
*" EXCEPTIONS
*"      WRONG_FUNCTION_CALLED
Check if you have different one. Even if the name of variables is not as above you may get the error message .
Cheers

Ale/idocs in hr

HI,
will any body tell the procedure for the ALE/DIOCS in HR,how to handle the custom idocs,extended IDOCS,standard idocs.
if any body have docs send it.it will really help full to me.

Hi,
The ALE/IDOC process is same in HR as in other modules. Search SCN, you ll find mant threads regarding how to configure the ALE/IDOC.
For HR the message type is HRMD_A for HR to HR
HRMD_ABA for HR to non-HR.
The basic type available for HRMD_A is (HRMD_A01-HRMD_A07).
http://www.easymarketplace.de/online-pdfs.php
check the document "Timesheet and HR in Distribution Models" its useful.
Br/Manas

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

Two idocs are created for one output message type

hi all,
we are communicating our sap idocs to external system using ALE.It is working smoothly.
Our problem raises here,
.idocs are creating at the time of output type attachment for purchase orders.But rarely,two idocs are creating for one message type.It means two idocs are created for same Purchase order.It makes complications for the external system.
anyone can help me pls?
thnks in advance..........

thanks jurgen for ur reply,
jurgen, the second idoc is not an "ORDCHG",It is the replica of first idoc.This one has also "ORDERS" message type.The only difference between these idocs are the time.It means the difference between the time field segments of these idocs have only three(3)seconds difference.We think that its from the system error.If it is not from the system error pls give me the explanation.
thanks in advance.......

Posting multiple idocs of different IDOC/message type

Hi! ALL
It would be very helpful if you please provide your valuable suggestions...
I have 4 different file to IDOC mappings and i am trying to post all the 4 using the same interface determination....out of the 4 ....2 IDOC are of the same message type...this is throwing out an error...
<SAP:Code area="IF_DETERMINATION">CX_ID_PLSRV</SAP:Code>
<SAP:P1>Inbound interface was found more than once (for same sender and receiver) for outbound interface http://ck.com/xi_com/Ship.MI_SHIP</SAP:P1>
<SAP:P2 />
I am trying to use 3 File IDOC mappings in the same Interface determination, for example has the following inbound receivers in the interface determination:
DESADV
WMMBXY
DESADV.........I am using DESADV twice as the Message Mapping is different for each of the inbound DESADV idoc
Please, let me know...if you were able to post similar message type IDOC in the same inteface determination.
Your help is greatly appreciated....
Thank you,
Patrick
Thank you

Hi! Bill
I am using 3 message interface(in 1 interface determination) and i am able to post 3 idocs....the problem only arises when the 4th idoc is of the same message type as any of the first 3.
I am trying to exclude the 4th mapping.....b'cos the issue with similar message/idoc's type issue.....but incase u have a solution let me know...here is an example
Eg:
DESADV
WMMBXY
SHIP...is posting fine!!
But...problem with..posting...
DESADV
WMMBXY
SHIP
DESADV(4th same as first)
And again as mentioned...each have there own message mapping(MI) and interface mapping(IM)....and are in the same interface determination...as outbound interface and BS is the same for and in the inbound as u know is IDOC..R3.
Thank you for your response....
Patrick

ALE settings error "Too many recipients found for message type" urgent

Hi all ,
please help me to solve this issue !!!!!!!!
i done with ale settings .
in the bd64 , orders message type is used in 2 different model view for 2 different systems
when i create po it is giving error in output "Too many recipients found for message type ORDERS in the ALE model"
how can i rectify this error.
Thanks

Hi,
Try to redefine your distribution model to have both receivers of your message type ORDERS in one "model view".
Regards,
Jakub

What is Message Type & IDOC Type?

He Experts!,
What is Message Type & IDOC Type? What is the difference between them?
Thanks in advance.
Sekhar

Hi,
Please try these transaction codes.
WE82 - Message Type and IDoc Type
WE64 - Process Codes (Inbound and Outbound) for Message Type.
Message type. A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterizes the data sent across systems and relates to the structure of the data called an IDOC type (see below). For example, MATMAS is a message type for Material Master, and INVOIC is a message type for an Invoice (Billing Document). ALE supports over 200 message types in R/3 and about 200 application areas.
IDOC type and IDOC. An Intermediate Document (IDOC) type represents the structure of the data associated with a message type (DEBMAS02 for message type DEBMAS Customer Master, and WMMBID02 for message type WMMBXY Goods Movements), while an IDOC is an object containing the data of a particular message type. IDOCs are data containers with intelligence built in. Each IDOC contains one and only one business object. For example, an IDOC of type SHPMNT01, message type SHPMNT, will contain data only of one Shipment Document. Generally, the architecture of an IDOC is independent of the message type by virtue of ALEs ability to redefine it for any message type.
Use transaction BD64 or the following menu path to maintain the model: From the IMG (Implementation Guide), Cross-Application Components -> Distribution (ALE) (*) -> Distribution Customer Model -> Maintain Distribution Customer Model Directly -> Maintain Distribution Customer Model Directly.
Thanks,
Sankar M

Ale with user created message type

Hello,
I have a created a segment ,idoc and message type and done the assignment of Idoc with message type also.
i have to send the material 800 to 810 client through ALE.
By using the Standard Message type MATMAS i m getting the material on 810 client.
But when i am using my message type ie ZMAT_MSG in tcode BD10 on client 800 to send the material it is saying error that message type does not exist.
I am not getting the problem
Or it is not possible to use your message type to send the material through Tcode BD10.You have to always use the standard message type MATMAS.
If yes then how to use our own message type to transfer the data from client 800 to 810.
Please reply .
Manish

Hi Vasu,
Please try this.
1. Create distribution model (BD64) for message type MATMAS_BAPI.
2. Create inbound partner profile (WE20) for message type MATMAS_BAPI and IDoc type MATMAS_BAPI01 and process code BAPI.
3. Create IDoc ports (WE21)
4. Setup RFC destination (SM59).
Hope this will help to start with.
Regards,
Ferry Lianto
Please reward points if helpful.

ALE-IDocs: Issue on COGRP1 & COGRP6 Message Types

Similar Messages

Maybe you are looking for