IDOCS types in R/3 system

Hi ,
can you please let me know how many types of IDOCS are there in R/3 system.
Thnx
Andy

Hi,
The following are the types of IDocs
General   -        Message types / IDoc types / BAPI
Vendor    -        CREMAS / CREMAS02
Customer -        DEBMAS / DEBMAS03
Accounting -            Message types / IDoc types / BAPI
G/L accoun -            GLMAST / GLMAST01
Cost center -            COSMAS / COSMAS01
Cost element -            COELEM / COELEM01
Cost center group -      COGRP1 / COGRP01
Cost element group -     COGRP1 / COGRP01
Activity type        -     COAMAS / COAMAS01
Activity group     -     COGRP1 / COGRP01
Activity price     -     COACTV / COACTV01
Profit center      -     PRCMAS / PRCMAS01
Profit center group -     COGRP1 / COGRP01
Profit center account group - COGRP1 / COGRP01
Logistics   -              Message types / IDoc types / BAPI
Article master - ARTMAS / ARTMAS02 / RetailMaterial.Clone
Additional -MMADDI / MMADDI01 / RetailMaterial.SaveAdditionalReplicas
Product catalog     -     PRDCAT / PRDCAT01
Product catalog item -     PRDPOS / PRDPOS01
Price list     -     PRICAT / PRICAT01
Assortment     -      ASSORTMENT / ASSORTMENT01 / Assortment.SaveReplica
Material master     - MATMAS / MATMAS03 - (See Template)
Service master     - SRVMAS / SRVMAS01
Characteristic     - CHRMAS / CHRMAS02
Class          - CLSMAS / CLSMAS03
Classification     - CLFMAS / CLFMAS01
Document     - DOCMAS / DOCMAS04
Purchasing info record - INFREC / INFREC01
Conditions     -     COND_A / COND_A01
Order book     -     SRCLST / SRCLST01
Change master     -     ECMMAS / ECMMAS01
Bill of material -     BOMMAT / BOMMAT01
Document BOM     -     BOMDOC / BOMDOC01
Work breakdown structure -      Project / PROJECT01
Human Resources - Message types / IDoc types / BAPI
PA object type person     -      HRMD_A / HRMD_A03
PD object types          -      HRMD_A / HRMD_A03
Basis      -          Message types / IDoc types / BAPI
User master record - USERCLONE / USERCLONE01 / User.Clone
Rgds,
Jothivel.
Note: Pls provide some valuable points if you are satisfied.
Message was edited by: Jothivel Sundaram

Similar Messages

Copy IDOC Type to another SAP System

Hi Team,
We want to copy a basic IDOC type WGSREQ02 from our ECC system to the BI system. The intent is to use this IDOC as an outbound from the BI system and then recieve it in the ECC system. Since we want to use it only as an outbound, we don't really need any application logic in BI. We just need the IDOC structure and the outbound capabilities so that we can use the application logic provided by default in ECC.
Please let me know if there is a way to copy the IDOC Definition from ECC to BI system.
Thanks
Sanjay

Hello Sanjay
I would use the following approach:
(1) Generate XML structure (XSD schema) from the IDoc type (on the ERP or via SAP-XI)
(2) On the BI system fill the empty XML with the data and make the transformation
back to IDoc structure (EDIDC and EDIDD)
But how to send these IDoc data via ALE? You need to define the IDoc type (which does not exist on your BI system) as outbound parameter of the partner profile (e.g. ERP as logical system).
Perhaps you can send the IDoc data using fm MASTER_IDOC_DISTRIBUTE.
Regards
Uwe

Create IDOC Type ORDERS in BackEnd System

Hello together,
we use " extended classic scenario" in our SRM 4.0 and replicate PO's in the ECC 6.0 ERP Backend System. We would like create during the replicat a Message Type (IDOC) ORDERS in Backen System. I háve customized (NACE / MN05) but it is not poosible to generate a IDOC. I have read it is necessary to activate a USER-EXIT for BBP PO's.
My question:
Which USER-EXIT and how must i create this!
Thanks for Answer!
Regards,
didisap
Edited by: Dietmar Blome on Feb 8, 2011 11:59 AM
Edited by: Dietmar Blome on Feb 8, 2011 12:01 PM

Hi,
Pls refer to following links for sample code ->
Re: Status distribution incorrect in GOA
Re: Distribution of GOA in R/3
Re: GOA Distribution SRM 5.0-ECC 6.0 - Account Category & Multiple Distribution
Re: Source determination in backend (R/3) for distributed contract i.e. GOA
FM or BADI s' used to create a GOA
BR,
Disha.
Do reward full points for useful answers and close the thread if your query is answered.

Is it Possible to import an IDoc type from R/3 into APO system

Hi Gurus ,
Could you please guide if we can import an IDoc type from R/3 system to APO system ?? If yes , can you please give the guidelines / step - by - step procedure for this.
Thanks in advance ,
Roseline

hi
yes u can export an idoc from r/3 to a legacy system.
the brief outline is as follows:
1. set up an rfc connection. it has to be 'T' type in t-code sm59
configure the saprfc.ini file if on windows based os. if on unix based os configure rfcexec.c to have the login details of apo system.
2.set up logical systems( at least 1 each for r/3 and apo) using T-code SALE.
3.assign clients to the logical sytems using T-code SALE..
4.create ports using tcode we20.
5. create idoc segments using we30 and release.
6. create idoc type using we31.
7. create message type using we81.
8. assign message to idoc using we82.
9.build a customer model using tcode bd64.
10. create an outbound process code usint tcode we41.
it will help if you specify your idoc that you want to use- for vendor, customer and material there are predefined distributions and idocs.
Thanks.

Idoc Type Mismatch in Source & BW Systems

Hi Friends
My problem goes as follows
I have BW development system and R/3 Development systems.Both this comination was working fine.Suddenly we had system copy of R/3 Production on R/3 Development for some testing.Now BW source system turns inactive.When i try to activate its gives following message.
'BW Idoc Type A is not equal to source system Idoc Type B'.
So using transaction WE30 i mainatined Idoc Type A in source system.But still it gives same error on activation of source system.I am stuck up here
Would u people plz help me with this urgently.Waiting for ur response.
Raghu

See the below link
BW idoc type not same as source system idoc type
After this try to restore the connection
Regs
Gopi
Assign points if it helps ...

Multiple message types for an idoc type

Hi all,
I created one custom idoc type with six segments. I heard that one idoc type can have any number of message types
if it is so pls tell me how to assign these two message types for my idoc .
i want to create multiple message types because i want to send same idoc type to diff legacy systems.
My requirement is message type one is only for first three segments and message type two is for another three segments .
The outbound program 1 for mess type 1 should fill fill the data for only first three segments and second outbound program corresponding to mess type 2 should fill the data for last three segments
how should i design for my requirement. suppose if the idoc has two message types then it has two outbound programs?

Hi Kunal,
Below are my thoughts from a design perspective,
My requirement is message type one is only for first three segments and message type two is for another three segments .
The outbound program 1 for mess type 1 should fill fill the data for only first three segments and second outbound program corresponding to mess type 2 should fill the data for last three segments
Before you look upon the no. of message types you need, i guess you need to look at the business requirement. Per your requirement you want to send send two sub sets of data. The first subset in the first 3 segments and other three segments for the second subset of data.
Is the structure of the first subset of data similar to the second subset If not, better to create two IDOC Types. If they are similar, then create one IDOC Type with three segments and have two message types for each subset of data.
For Ex: ORDERS05 is the IDOC type for Orders, this IDOC type provides capability to carry data related to any type of orders
but the action on the data is facilitated by the message type like ORDERS for create, ORDCHG for change, ORDRSP for Order response etc.
OR
Are these two subsets of data related to each other, if yes understand the relation? If not related at all then you might be better of creating two separate IDOC Types.
Like in the above example A purchase order is related to a sales order so you can use the same IDOC type, but in case of a order response and ASN that data sent is different and hence you will need different IDOC types (even though a SO is related to a DN).
how should i design for my requirement. suppose if the idoc has two message types then it has two outbound programs?
The above again depends on the how tightly/loosely coupled are the data sets, you can have just one program and have a simple case statement on the message types or have two different programs.
You will also have to consider points like, if any of the subsets is more prone to more change in terms of the structure and associated business logic. If yes, then you might want to keep the programs separate to reduce work on regression testing etc.
I am sure you will receive more inputs from the experts on the forum and the list of points to look for will get longer , so understand the requirement, dependencies and if you have any specific questions you could post it on the forum.
Regards,
Chen

IDOC type DEBMAS06 change pointer

Hi,
I am working on idoc to file scenario.
I want to create/send idoc DEBMAS06.It is possible to send all segment of idoc using change pointer.
I am changing customer using XD02,and it send only 2 segment in idoc.There is require ment to pass all segment whenever there is any change in customer data.
Regards
Mohit

Hi Rajesh,
Thanks for your reply.
I have tested bd12 and now it shows more segments then before.
But i need to send idoc automaticaly to pi system ,Is there any way to do so.
Right now i have activated chnge pointer and schedule back ground job RBDMIDOC to send idoc type debmas06 to pi system.
regards
Mohit

RSAR2318 : IDoc type for source system T90CLNT090 is not available

Hi all,
I am working on BI + ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
1. Error:
R7I028
Object could not be activated
2. Error:
RSAR238
IDoc type for source system T90CLNT090 is not available
Error when creating the export datasource and dependent objects
Error RSAR238 : IDoc type for source system T90CLNT090 is not available
I have already checked trx & dtps, but could not find resolution.
Kindly help me with this error.
Thanks and regards,
MS

M Sharma wrote:
But how exactly can I create when T90CLNT is not active? Help please.
Yes, you would need to check with BASIS team how they have created an alternate source system (for debugging) & prepare a RFC b/n these systems. Can you just check the settings in the source system and BI source system...and check the source system for the same BI system. Right click > Check and then do a restore or take the help of basis to fix it. What I think is a possible solution is : RSA1 > Source system > Search System > Right Click > Activate

RSAR238 : IDoc type for source system T90CLNT090 is not available

Hi all,
I am working on ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
1. Error:
R7I028
Object could not be activated
2. Error:
RSAR238
IDoc type for source system T90CLNT090 is not available
Error when creating the export datasource and dependent objects
Kindly help me with this error.
Thanks and regards,
Dhanapal

Hi,
Check the same in SDN..
Object ZDUMMY could not be activatedMessage no. R7I028
Re: DSO Activation problem
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/test-cases-for-module-human-capital-management-1425016
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/idoc-type-for-source-system-t90clnt090-is-not-available-message-no-rsar238-1431565
Thanks
Reddy

Source System Activation - IDOC Type does not exist

I'm doing a new installation of BI7 and when I want to activate the source system on replicate Metadata Box and select "Only Activate" it comes up with error stating :Basic Type ZSxxxxx does not exist
When I look in SE16 on table RSBASIDOC I can see the IDOC Type exist on both BW and R/3 Systems
Any solution?

Check my reply
Re: "Basic Type Does Not Exist"

ALEREQ idoc type from PI system

Hi,
I have to change the vendor data from Inbound idoc which will be coming from PI system.
but, to get the inbound idoc for vendor we have idoc type as CREMAS05 and message type as CREFET
But,at PI side to send the vendor data, they see the idoc type as ALEREQ01 for message type as CREFET.
Kindly provide me the resolution.
Thanks in Advance.

hi
yes u can export an idoc from r/3 to a legacy system.
the brief outline is as follows:
1. set up an rfc connection. it has to be 'T' type in t-code sm59
configure the saprfc.ini file if on windows based os. if on unix based os configure rfcexec.c to have the login details of apo system.
2.set up logical systems( at least 1 each for r/3 and apo) using T-code SALE.
3.assign clients to the logical sytems using T-code SALE..
4.create ports using tcode we20.
5. create idoc segments using we30 and release.
6. create idoc type using we31.
7. create message type using we81.
8. assign message to idoc using we82.
9.build a customer model using tcode bd64.
10. create an outbound process code usint tcode we41.
it will help if you specify your idoc that you want to use- for vendor, customer and material there are predefined distributions and idocs.
Thanks.

BI Idoc Type IS NOT THE SAME AS SOURCE SYSTEM IDOC TYPE

Hi all,
how can we solve the IDoc miss match in source system (ECC6).
Error :
BI Idoc Type ZSTC029 IS NOT THE SAME AS SOURCE SYSTEM IDOC TYPE ZSTC031
please provide me solutions..
Thanks in advance,
Venkatesh

Hi Venkatesh,
Check here.........
BW idoc type not same as source system idoc type
Thanks,
Vijay.

Incorrect IDoc type ZSWA003 in the ALE defintion of the source system.

Hi !
When I triggering the load from BW it is giving me an error Incorrect IDoc type ZSWA003 in the ALE defintion of the source system.
When I am checking the connection in source system with R3 system , it is giving me this error and asked me to Enter IDoc type ZSWA011 .
Please tell me how to do this.

Hi,
I assume that the source system has been copied fom production onto quality-system (or somothin likely).
To solve that, plase refer to the oss-note 886102.
https://websmp130.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=886102
https://service.sap.com/sap/support/notes/886102
Hope that helps.
cheers
Sven
Edited by: Sven Muntermann on Mar 26, 2009 6:21 PM

Incorrect IDoc type ZSBB010 in the ALE defintion of the source system.

Hi,
We have done client copy of BW production system into BW test system.
I am getting following error while checking Test R/3 system in BW Administrator workbench.
Diagnosis
Incorrect IDoc type ZSBB010 in the ALE defintion of the source system.
System response
Error when sending data to BW.
Procedure
Enter IDoc type ZSBB017 .
Ring any bell.. Thank you for Ur time..
Cheers
Senthil

Hello Senthil,
Please check WE20 transaction and look for idoc type there.Most likely you need to make some corrections in there. Also check BD64.
Regards.
Ruchit.

Incorrect Idoc type ZSPA065 in the ALE definition of the source system RSAR

Hi Experts,
Incorrect Idoc type ZSPA065 in the ALE definition of the source system RSAR 373 error is coming .
Some one suggested note no 886102 but i went inside i did not find correction or code for implementing please any body suggeste for rectifying this error.
Please tell correct aproach for solving the issue.

Hi,
there is some problem with your RFC connection
just go to WE20 T code and expand partner type LS
here search your r/3 system and click on that here you can find the details of idoc
if you are not able to correct yourself you can contact basis team for that.
just go to RSA1--> using the conxt menu doa check of Source system you will get the error message
just send the screen shot of the same to Basis team they will take care of the same.
Br
santosh

IDOCS types in R/3 system

Similar Messages

Maybe you are looking for