RC1_IDOC_SET_STATUS Program - Message Type & Idoc Number

Hi All,
Good Morning.
We use the SAP Standard Program RC1_IDOC_SET_STATUS to convert the status of Idocs. Recently, we had encountered a behavior which we havent come across before.
The selection screen has the IDOC number, the message type, the current status and the new status. There is an additional trial run checkbox as well.
(1) If the IDOC number alone is given then the status of that idoc alone will be changed. (And that works successfully)
(2) If the message type alone is given then the status of the Idocs for that message type are converted (And that works successfully)
(3) If the message type and the Idoc number is given, then the program converts the status of the all the idocs associated with the message type irrespective of the specification of IDOC numbers in the selection screen. (Now, this is where we faced the problem, the system converted all the Idocs with the mentioned message type ignoring the list of Idocs to be changed).
This resulted in change of the status of all Idocs of a particular message type.
Is there a way, we could track the Idocs which got changed and reverse them back to the old status? Is there an SAP note which addresses this issue?
Your Inputs on this would be highly appreciated.
Spandana

Hi,
With this report , specifying range won't work because the program loops at the select option and only takes the LOW variable of each record. So it is necessary that you pass all the idoc numbers for which you want to change the status for.
The solution is to give exact idoc numbers in the single values or copy this program to a 'Z' program and tweak it as per your requirement.
Br,
Advait

Similar Messages

Any Idea Which Message type/Idoc Type should be used for FI Invoice

Hi Experts,
Any idea what message type/Idoc type should be used for FI invoice. We are going to send IDOC from R/3 to Non-SAP System using ALE. We are using T-codes FV60/FV65.
Thanks,
Sony

Hi Sony,
I never dealt with FI IDoc.
I think you need to setup EDI outgoing payment in IMG. Please take look this report RFFOALE1 - ALE Distribution of Payment Data and RFFOEDI1 and check also the program documentation.
Hope this will help.
Regards,
Ferry Lianto

Please provide the Message type ,IDOC TYPE , PROCESS CODE for Edi 990 ,214

Hi friends,
Please provide the Message type ,IDOC TYPE , PROCESS CODE for Edi 990 (Response to a Load Tender)., 214 (Shipment Status )
For shipement status i got trxstc01 for idoc type .. but its only before 4.6 version ..for 4.7 its not there .. please give the alternate for that ...
Thanks in Advance ....
If any one is provide exact answer i will give Max marks ..
Edited by: ajay KOLLA on Aug 6, 2009 8:04 AM

Hi,
Have you resolved this issue. If yes, can you please let me know. Im actually looking for same for EDI 867 (guess it is for summary report and need to know message type, Idoc type associated with this).
Rgds
Sudhanshu

Message type ,IDOC TYPE , PROCESS CODE for Edi 990

Hi ,
Please provide the Message type ,IDOC TYPE , PROCESS CODE for Edi 990 (Response to a Load Tender).
Thanks in Advance.
Ajay Kolla

Hi
Pls check the below links
1. http://www.erpgenie.com/sap/sapedi/ansi.htm
2. http://www.erpgenie.com/sap-technical/ale-edi-b2b/master-data-message-types-idoc-types
Hope this may helps you.
Regards
Sirigiri

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

Message with IDOC number, created by LSMW, missing in job log in SM37

Hi gurus,
We have a temporary interface which uses LSMW to create IDOCs and update in SAP. It's used for materials, BOMs and document info records. In LSMW we have defined standard message types MATMAS_BAPI, BOMMAT and DOCUMENT_LOAD for the IDOCs. All these have the same problem.
A background job runs and starts LSMW. In the job log in SM37 I want to see which IDOCs were created. For some reason this is different in my development system and my test system, and as far as I know all settings should be the same. In the test system LSMW creates more message lines in the job log, than it does in the dev system. Message number E0-097 is "IDOC XXXX added", and this is missing in the dev system.
This is what it looks like in the dev system:
Data transfer started for object 'MATMAS' (project 'X', subobject 'Y')             /SAPDMC/LSMW   501    I
Import program executed successfully                                                             /SAPDMC/LSMW   509    I
File 'XXX.lsmw.read' exists                                                                               /SAPDMC/LSMW   502    I
Conversion program executed successfully                                                    /SAPDMC/LSMW   513    I
Data transfer terminated for object 'MATMAS' (project 'X', subproject 'Y')       /SAPDMC/LSMW 516    I
And this is what it looks like in the test system. More information, which is exactly what I want in dev system too:
Data transfer started for object 'MATMAS' (project 'X', subobject 'Y')             /SAPDMC/LSMW   501    I
Import program executed successfully                                                             /SAPDMC/LSMW 509    I
File 'XXX.lsmw.read' exists                                                                               /SAPDMC/LSMW 502    I
Conversion program executed successfully                                                    /SAPDMC/LSMW 513    I
File 'XXX.lsmw.conv' exists                                                                              /SAPDMC/LSMW   502   I
IDoc '0000000002489289' added                                                                      E0                         097   S
File 'XXX.lsmw.conv' transferred for IDoc generation                                      /SAPDMC/LSMW   812   I
Data transfer terminated for object 'MATMAS' (project 'X', subproject 'Y')      /SAPDMC/LSMW   516   I
In both cases the IDOC is created and update works fine.
My only issue is that I can't see the IDOC number in the dev system. I know I can get the IDOC number in WE02, but in this case we have program logic which reads the job log to be able to check IDOC status before sending OK message back to the other side of the interface.
I hope any of you can have an idea how I can update somewhere to get message E0-097 with IDOC number into the log.
Regards,
Lisbeth

Hi Arun,
If you want to show your messages in the job log you have to use the MESSAGE statement. In case you use WRITE statements an output list be created which can be found in the spool (there is an icon to go to the spool directly).
Regards,
John.

Message type, Idoc type and process code in ALE/Idoc

Each Idoc version(creams01 or cremas03) will have seperate process codes in Inbound process?
Whether Message type triggers the process code or the Idoctype/idoc triggers the process code in Inbound process?
regards
Message was edited by: henry

Hi Henry,
About your question as how should you assign seperate process code for the same message type ( with different IDoc Type )-
In We42, the message type can be assigned to the processing code. But here you will find that along with message type there are two more fields - Message Code & Message Function.
You can use any one these to serve your purpose.
e.g. you can assign
-process code P1 to message type M with Message code 1
-process code P2 to message type M with Message code 2
Further these process types can be configured to call separate FMs.
Now depending on IDOC types your external system should populate the message type as well as Message code so that accordingly process code will be determined at the time of inbound processing.
I hope it's clear & correct
Thanks,
Ram

What are some of the message types (IDocs) related to HR in SAP?

Hello all,
Please tell me where can I get more details?
Thanks,
Charles.

Hi Charles,
Here is some material which i read some time ago, i think this will be helpul to you for IDOC, this may not give whole idea but atleast some basic ,
You need to get in touch with ABAP person for IDOC,
To create an Outbound interface from SAP HR to Other System.
*You have to know the process completely. I will give you the explanation here....*
*First of all you have to findout the Messgae type and IDOC type for the data.*
*Message Types:*
*Suppose if u want to transfer*
*Master and Organizational data----> HRMD_A*
*Personnel Actions -> HRSM_A*
*Time data---HRSM_C/HRSM_D*
*IDOC Types:*
*These stuff you can findout in WE30 Transaction code.*
*For HRMD_A----> HRMD_A01*
*HRSM_A----> HRSM_A01*
*If u go inside by selecting the IDOC type u can view all the segments.*
*For individual Segments you can go to the Transaction code WE31*
*Note: Suppose if the standard segments or IDOC type doesn't support your req..u can create the custom stuff in the same transaction code itself.*
*After completion of this,with the help of BASIS team you have to configure the ALE settings between the HR and Siebel system. And also make sure all the Outbound and Inbound parameters are defined correctly.*
*Then try to send the Master data using the Transaction code PFAL.*
*In this TCODE you can send the data based on Object type,Object ID,Infotype/Subtype etc...*
*If you are missing anydata from here try to customize the Inbound function module by the help of HR ABAPer.*
*(Normally we will go for standard FModule IDOC_INPUT_HRMD_A01....).* Bye let me know if you find this helpful
Regards
Pallavi

Message types(IDOC) in XI

Hi,
I am trying to maintain distribution model in XI, i could not found message types CREMAS, MATMAS and DEBMAS. can anyone help.
Actually i am sending IDOC's from R/3 to XI, i create RFC OUTBOUND in R/3 and maintained distribution model view.
Thanks in Advance
srinivas

hi,
>>>>I am trying to maintain distribution model in XI,
you do not do that in XI as it doesn't make any sense to use it there - XI does not store any master/transactional data
Regards,
michal

Message type idoc type problems

Hi,
I'm facing a problem in idocs. I'm sending idocs with message type ORDRSP and idoc type ORDERS05, but for some reason in SAP, the idoc is always picking up a different message type ORDERS and the partner profile part is failing because my partner profile is set up for ORDRSP message type. Is there any setting or transaction that sets a default message type for an idoc type in SAP.
Regards,
Vijay

Hi vihay,
yes for the message type ordrsp the basic type is orders05.
u r telling ur geeting problem in inbound idoc?
if that is the case then u have to use in we20 inbound parameters and give the processcode(ORDE) there instead of basictype .CHECK the same and get back to me if any quries
Regards,
Nagaraj

Problem to create change pointer for custom message type - Idoc creation

Hi,
We want to create IDOC and send it out when the data of "planning calendar" changes. So we are trying to generate change pointers whenever entries in Table T439I (Planniing calendar) data change.
We created a message type, activated change pointers generally and maintained change relevant fields for message type (not sure if this step is done correctly). But not getting any change pointer in table BDCP2 when I create a new planning calendar in MD25.
Can anybody help / guide?

Thanks once again,
I had linked idoc type and message type in we82. Now after i activate the change pointers. I try to generate the IDOC type using BD21. It gives me the error message : "Message type ZP2PPROJ_MSG cannot be sent with change pointers"
whereas in my segments i am using all the master data only (i.e. PRPS, PROJ,PRHI). Please throw some light on this.
Also please clarify, do i need to make an entry of this custome message type in the partner profile ?
Rgds
kewal.

Reduced message type - Idoc without conversion rules

Hi Friends,
Am facing a strange situation while converting the Material Master data from 4.7b to ECC using BD21 transaction with reduced custom message type. I have reduced the standard msg type MATMAS05 using BD53 for the required field mapping both systems and I written the code using the exit EXIT_SAPLMV01_002 based on client req.
The situation is that sometimes IDocs are failing and the error shows that some fields which I have not selected in E1MARAM segment of the reduced msg type are populated with some values(ex: zeroes-0, slash-/,spaces)
Note: Conversion rules are not needed for this scenario.
Please help me out how to get rid of this '/ ' or spaces which appear for unselected fields in outbound Idoc using reduced message type ?
Thanks
Saravanan

Hi,
Please check the documentation in WE60 tcode and see if the fields are required to be passed...
Regards,
Nagaraj

Message type idoc type

for purchase order wt is the standard message type and what is the standard idoc type used

hi,
in WE30/WE60, search for PORD*.
You will get a list of all the purchase order idoc types.
In WE82, you can view the IDOC Type and Message type combination.
Regards,
Subramanian

Message Type ( Idoc Type ) for customer master & Pending invoice

Hi
My Client is doing sale in POS for credit customers and credit customer master should be sent to POS as outbound Idoc.
1.What is the standard message type for sending Customer masters to POS. WP_PER01 is not activated for version 700 ( message getting on WE60 ). Plse let us know is there any another message type for customer master.
2. Also i need to send the credit limit of the customer to POS . Is this possible by standard message type or we need to go for ZIdoc?.
3.Is there standard Outbound Idoc ( Message type ) available to send the Pending invoice list toPOS?
plse help me on the above
Regards
Anis

Hi ,
you can use DEBMAS message type for customer master IDOC ,
Tcode Bd12
Thanks,
Amit

Confirmation - Message type - Idoc

Hi,
Please le me know how the Idoc ( MBGMCR01 ) is triggered for the SRM confirmation, Whether any back end tranaction exist for confirmation? I have to replace the standard Idoc with a custom Idoc so Please let me know how to do it.
regards,
Prabhu

Hi Prabhu,
in transaction WE30 you can define your customer own IDOC types; then you need to add it to a partner profile in txn WE20. Under partner type LS (logical system), you can find the related backend systems; the message type under 'outbound parmtrs.' is MBGMCR. When you double click on it, you can see the field 'basic type' where you can select the Z-type via F4 help.
Basically there´s no SRM-backend transaction for SRM confirmations. I only know the standard MM transaction MIGO where you can post goods receipts to PO´s etc.
When posting a confirmation in classic or extended classic scenario in SRM, then you will find a local SRM confirmation and a backend goods receipt which is created via IDOC in the material case or vial BAPI_ENTRYSHEET_CREATE in the service case.
Kind Regards
Michael

RC1_IDOC_SET_STATUS Program - Message Type & Idoc Number

Similar Messages

Maybe you are looking for