Difference between CREMDM04 Idoc and CREMAS04 Idoc

Hi all,
I am creating a vendor using an idoc CREMAS04.
But there are some fields which are not there in that IDOC (fields like Email address , POBOX number for other country) so i want to know that is there any other IDOC which contains all the fields for the vendor creation.
I have found the IDOC CREMDM04 which contains those fields but i want to know the difference between the CREMDM04 and CREMAS04.
I also want to know that will it make any difference is i use CREMDM04 instead of CREMAS04(like is it that all the fields of CREMAS04 is there in CREMDM04 or no).
If anybody knows ,then please let me know.
Thanks in advance.
Shruti.

to name a few:
CREMAS01 Vendor master data distribution ALE
CREMAS02 Vendor master data distribution ALE
CREMAS03 Vendor master data distribution
CREMAS04 Vendor master data distribution
CREMDM01 MDM: Mass Processing CREMAS (Vendor Master)
CREMDM02 MDM: Mass Processing CREMAS (Vendor Master + Addresses)
CREMDM03 MDM: Mass Processing CREMAS (Vendor Master + Addresses)
CREMDM04 MDM: Mass Processing CREMAS (Vendor Master + Addresses)

Similar Messages

Difference between message type and idoc type

Hi
difference between message type and idoc type
Regards
Rama

Hi,
Message Type:
A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterises the data sent across systems and relates to the structure of the data called an IDOC type.
Diff. with IDOC type
An IDoc type specifies the structure of the data.
A message type specifies the meaning of the data
Diff. b/w IDOC type and IDOC
An IDoc type is the definition of a specific data structure.
An IDoc is an actual instance of data based on an IDoc type. Therefore, there can be many IDocs created from a single IDoc type.
Example:
MATMAS is the message type and MATMAS05 is IDoc type for Material Master.
Thanks,
Shankar

Principal difference between an Idoc and a Switch document.

Hello
what is the principal difference between an Idoc and a Switch document.
Thanks

Hi,
A switch document documents a process, such as, switch of supplier, in a liberalized market and can be monitored with own transactions. The process steps are usually controlled by workflows.
An IDoc is used to transfer data from one system to another one in a predefined package. When you import an IDoc containing a market message, a workflow can be started creating/updating switch documents.
Kind regards,
Fritz

Difference between Master Idoc and Communication Idoc.

Can anyone list out the difference between Master Idoc and Communication Idoc?

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
Form and content: IDoc terminology
As is often the case with proprietary technologies, SAP assigns specific, object-oriented meanings to familiar terms. When referring to IDocs, the term document refers to a set of data comprising a functional group of records with a business identity. (For example, all the data in a purchase order, or all the profile information of a supplier in a supplier master record.)
A message refers to the contents of a specific implementation of an IDoc; its a logical reference. This differs from a reference to the IDoc itself, which specifies the messages physical representation. Think of it this way: If youre watching a parade pass by, the mayor waving to the crowd from his limousine is the message, and the mayors limousine (which is specific to the mayor) is the IDoc. Youre building a logical object, and the IDoc is both its container and the vehicle that moves it.
The IDoc control record
Each IDoc has a single control record, always the first record in the set. The structure of this record describes the content of the data records that will follow and provides administrative information, such as the IDocs functional category (Message Type/IDoc Type), as well as its origin (Sender) and destination (Receiver) as in conventional EDI
Layout of an IDoc control record
This cover slip format informs the receiving system of the IDocs purpose, and the receiving system uses it to determine the correct processing algorithm for handling the arriving IDoc.
Data records
The data records following the control record are structured alike, including two sections: a segment information section and a data section.
In the first part of a data record, the segment information section describes the structure of the data that follows, for the benefit of the IDoc processor. There is a segment name (like an EDI segment identifier) that corresponds to a data dictionary structure to which the IDoc processor has access. The remaining information is useful for foreign systems, such as a partner companys Oracle system, which has no such data dictionary.
The second part of the record is the data itself, a storage area of 1,000 characters.
Status records
If youve ever ordered a package from a faraway location and tracked its progress using the Internet-based tracking utilities now provided by most major parcel carriers, youre familiar with the list of stops and transfer points through which a package passes on its way to you.
This collection of records is exactly what youll see in an IDoc that has begun its work. Following the data records in an IDoc, status records accumulate as an IDoc makes its way from one point in a process to another.
Typically, an IDoc will acquire several of these records as its does its job. They are simple records, consisting of a status code (there are more than 70 codes, covering a broad range of conditions and errors), a date/time stamp, and some additional status information fields for system audit purposes. In addition, as errors occur in the processing of an IDoc, status records are used to record these errors and the date/time of their occurrence.
IDoc Base
IDocs, as data formatting tools, enable the easy sharing of data between databases and applications within a company as well as being an efficient data courier between companies. Typically in SAP, a database of IDoc definitions exists, to which any application may have access.
This IDoc Base gives all the applications and processes in your company domain the capacity to send, receive, and process a document in a contextually appropriate way, without doing anything to the data. For example, a purchase order IDoc can filter through every process it touches, passing from system to system, accumulating status records to track its progress.
Every department using the data can use it appropriately without any cumbersome intermediate processes, because each department draws its key to interpreting the IDoc from the same source.
Multiple messages
One cumbersome feature of conventional EDI is the embedding of more than one functional record type in a document. The unwieldy X-12 888 Item Maintenance transaction set is an example: It purports to handle so many different configurations of product master data that it is horrifically difficult to integrate into an existing system.
IDocs, on the other hand, handle multiple messages with ease. Given the centralized IDoc interpretation that SAP provides to all its parts, its no problem to define an IDoc that will contain more than one message, that is, more than one data record type.
A customer master IDoc, for example, may contain customer profile information records for a customer with many locations. But it may also contain location-specific pricing information records for that customer in the same document. This is an incredibly efficient way of bundling related records, particularly when passing large amounts of complex information from system to system Records in a multiple-message IDoc

What is difference between BP monitor and supplier monitor?

hi friends
what is difference between BP monitor and Supplier Monitor
what is tcode for BPmonitor
Regards
Vinny

Hi Vinny,
Please refer to the following links. These seems useful:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f051efda-bc58-2910-3785-e60d1f798c96
The specified item was not found.
New Business Process Monitoring functionalities in SAP Solution Manager ALE / IDoc Monitoring
Regards,
Saumya

What's the difference between segment filtering and reduced message type

Hi gurus,
What's the difference between segment filtering and reduced message type? It seems they have the same functionality: Reduce the segment while idoc is generated.
Thanks in advance.

Hi,
BD53 is for IDoc Reduction.
this allows you to create a reduced message based upon a standard message type.If you want see mandatory fields. go to T-coe BD53 and give one standard messege type name and eg: matmas
there mandatory fields will be in Green color..
And BD56- This transaction is used to filter out segments of IDocs for combination of sender and receiver. This is usefull in scenarios where a standard IDoc with many segments is used but the receiving partner is only interested in some of the segments
the table related to this transation is TBD20
please go through below blog you have an idea abt that,
http://wiki.sdn.sap.com/wiki/display/ABAP/ReducedMessageTypes
http://saptotal.com/IDoc%20Segment%20Filtering.html
regards,
ganesh.

Difference between Seeburger FTP and OFTP adapters

hi,
Can anybody tell me the difference between Seeburger FTP and OFTP adapters?
On what basis should one make a business decision as to which adapter to go for?
Kindly help urgently.
Regards,
Loveena

Hi ! Loveena
Seeburger EDI Adapter provides an EDI solution on internet via HTTP or AS2 to replace the expensive VAN. It provides some pre-built mappings for IDOC to ANSI X12(810,850,855,856 etc.,) and Idoc to EDIFACT(ORDERS,DESADV,INVOIC etc.,) and has the ability to build your own. These pre-defined mappings transform the IDOC-XML to EDI-XML format.
Seeburger Adapters are used to Connect the applications which are using Message protocol/Transport protocol as CrossIndustry(payment), VAN, OFTP, AS2(EDIINT), Generic and EDI based applications.
Re: Seeburger Adapter
Reg seeburger seeburger
installation
https://forums.sdn.sap.com/click.jspa?searchID=2268965&messageID=3210111
OFTP ist a communication protocol. This has nothing to do with the format you have to transfer.
regards the format you have to clear at which standard you have to transfer the messages. This can be any EDI format. At OFTP area the standard are often VDA or ODETTE.
You can create this messages using different EDI adapters (of course also the mendelson adapter ).
Regards OFTP you need additional software which handle the transfer based on the OFTP standard. Mostly you also need an ISDN card for using this protocol.
We can support you with this software for OFTP transport too.
More info also available at http://www.mendelson-e-c.com/.
have a look at the ACTIS OFTP Adapter
Ref: http://www.actis.atosorigin.de/solutions/en/ACTIS_solutions/SAPXI.php
refer this thread also
When we need Seeburger AS2 & FTP?
XI Seeburger adapters
Adapter for OFTP?!
Thanks !!

Difference between R/3 and CRM systems

Hi,
I want to know difference between R/3 and other systems like CRM, SCM. Shall we need XI to integrate them..
I think that CRM,SCM are the modules of R/3 is correct..
What kind of applications they are...
Thanks,
RamuV

Hi Ramu,
As you said they are R3 Applications only.
can be connected with the help of XI.
CRM uses BDOCs but XI can only deal with IDOCs. So when you will be working with BDOCs of CRM, then in CRM you will have to create custom IDOCs for the corresponding BDOCs and then you can have File-IDOC and IDOC-file scenarios working via XI to communicate between your CRM server.
BestRegards,
Ramesh

Difference between RFC adapter and a proxy

Can any one tell me the technical difference between RFC adapter and a proxy?
reg

There are advantages / disadvantages for RFC / Proxies / Idocs. So if I am in your position depending upon the requirement I will choose one. Some of the differences are:
RFC and Proxy:
RFC/BAPI has its own overhead of function call.
Proxies communicate with the XI server by means of native SOAP calls over HTTP .RFC does not, so you have to convert from SOAP to RFC calls and vice versa. So XML conversion is required.
ABAP Proxies uses Webservice and Http Protocols.
If you use ABAP Proxy , you can reduce the overhead calling the function again and again.
Proxy and Idoc:
IDOC : After recieving the strucutred data It processes it using a Function Module associated with it.
Proxy : Proxy is a structure where there is no processing function module associated. You need to explicitly write the Business Logic/Call the subroutines here
This is my absolutely my view. Another guy has his own response. So first go through your requirements and then you can decide for what to go.
Also go through this urls which may help you:
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
RFC VS PROXY
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
Re: IDOC and RFC
Re: Proxy Vs IDOC
Thanks
Rodrigo

Difference between BW3.5 and BI 7.0 version

difference between BW3.5 and BI 7.0 version

Hi ,
Differences between BW 3.5 and BI 7.0
Major Differences between Sap Bw 3.5 & sapBI 7.0 version:
1. In Infosets now you can include Infocubes as well.
2. The Remodeling transaction helps you add new key figure and characteristics and handles historical data as well without much hassle. This is only for info cube.
3. The BI accelerator (for now only for infocubes) helps in reducing query run time by almost a factor of 10 - 100. This BI accl is a separate box and would cost more. Vendors for these would be HP or IBM.
4. The monitoring has been imprvoed with a new portal based cockpit. Which means you would need to have an EP guy in ur project for implementing the portal !
5. Search functionality hass improved!! You can search any object. Not like 3.5
6. Transformations are in and routines are passe! Yess, you can always revert to the old transactions too.
7. The Data Warehousing Workbench replaces the Administrator Workbench.
8. Functional enhancements have been made for the DataStore object:
New type of DataStore object
Enhanced settings for performance optimization of DataStore objects.
9. The transformation replaces the transfer and update rules.
10. New authorization objects have been added
11. Remodeling of InfoProviders supports you in Information
Lifecycle Management.
12 The Data Source:
There is a new object concept for the Data Source.
Options for direct access to data have been enhanced.
From BI, remote activation of Data Sources is possible in SAP source systems.
13.There are functional changes to the Persistent Staging Area (PSA).
14.BI supports real-time data acquisition.
15 SAP BW is now known formally as BI (part of NetWeaver 2004s). It implements the Enterprise Data Warehousing (EDW). The new features/ Major differences include:
a) Renamed ODS as DataStore.
b) Inclusion of Write-optmized DataStore which does not have any change log and the requests do need any activation
c) Unification of Transfer and Update rules
d) Introduction of "end routine" and "Expert Routine"
e) Push of XML data into BI system (into PSA) without Service API or Delta Queue
f) Intoduction of BI accelerator that significantly improves the performance.
g) Load through PSA has become a must. I am not too sure about this. It looks like we would not have the option to bypass the PSA Yes,
16. Load through PSA has become a mandatory. You can't skip this, and also there is no IDoc transfer method in BI 7.0. DTP (Data Transfer Process) replaced the Transfer and Update rules. Also in the Transformation now we can do "Start Routine, Expert Routine and End Routine". during data load.
New features in BI 7 compared to earlier versions:
i. New data flow capabilities such as Data Transfer Process (DTP), Real time data Acquisition (RDA).
ii. Enhanced and Graphical transformation capabilities such as Drag and Relate options.
iii. One level of Transformation. This replaces the Transfer Rules and Update Rules
iv. Performance optimization includes new BI Accelerator feature.
v. User management (includes new concept for analysis authorizations) for more flexible BI end user authorizations.
Regards
KP

What is difference between sy-tabix and sy-index.

SAP Seniors,
Can you please let me know what is difference between sy-index and sy-tabix.
I read the SAP help, it is confusing for me. it looks like both are same from help. please help me.
Thank you
Anitha.

HI,
Here is a brief description of difference between SY_TABIX and SY_INDEX and using them with several conditions.
SY-TABIX
Current line of an internal table. SY-TABIX is set by the statements below, but only for index tables. The field is either not set or is set to 0 for hashed tables.
APPEND sets SY-TABIX to the index of the last line of the table, that is, it contains the overall number of entries in the table.
COLLECT sets SY-TABIX to the index of the existing or inserted line in the table. If the table has the type HASHED TABLE, SY-TABIX is set to 0.
LOOP AT sets SY-TABIX to the index of the current line at the beginning of each loop lass. At the end of the loop, SY-TABIX is reset to the value that it had before entering the loop. It is set to 0 if the table has the type HASHED TABLE.
READ TABLE sets SY-TABIX to the index of the table line read. If you use a binary search, and the system does not find a line, SY-TABIX contains the total number of lines, or one more than the total number of lines. SY-INDEX is undefined if a linear search fails to return an entry.
SEARCH <itab> FOR sets SY-TABIX to the index of the table line in which the search string is found.
SY-INDEX
In a DO or WHILE loop, SY-INDEX contains the number of loop passes including the current pass.
Hope this helps.
Thank you,
Pavan.

Difference between sy-tabix and sy-index?

tell me about sy-tabix and sy-index?what is the difference between sy-tabix and sy-index?
Moderator Message: Please search before posting. Read the [Forum Rules Of Engagement |https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement] for further details.
Edited by: Suhas Saha on Jun 18, 2011 5:33 PM

HI,
Here is a brief description of difference between SY_TABIX and SY_INDEX and using them with several conditions.
SY-TABIX
Current line of an internal table. SY-TABIX is set by the statements below, but only for index tables. The field is either not set or is set to 0 for hashed tables.
APPEND sets SY-TABIX to the index of the last line of the table, that is, it contains the overall number of entries in the table.
COLLECT sets SY-TABIX to the index of the existing or inserted line in the table. If the table has the type HASHED TABLE, SY-TABIX is set to 0.
LOOP AT sets SY-TABIX to the index of the current line at the beginning of each loop lass. At the end of the loop, SY-TABIX is reset to the value that it had before entering the loop. It is set to 0 if the table has the type HASHED TABLE.
READ TABLE sets SY-TABIX to the index of the table line read. If you use a binary search, and the system does not find a line, SY-TABIX contains the total number of lines, or one more than the total number of lines. SY-INDEX is undefined if a linear search fails to return an entry.
SEARCH <itab> FOR sets SY-TABIX to the index of the table line in which the search string is found.
SY-INDEX
In a DO or WHILE loop, SY-INDEX contains the number of loop passes including the current pass.
Hope this helps.
Thank you,
Pavan.

What is difference between sy-index and sy-tabix and where both are using ?

what is difference between sy-index and sy-tabix and where both are using ?

hi nagaraju
sy-tabix is in Internal table, current line index. So it can only be used while looping at the internal table.
sy-index is in Loops, number of current pass. This you can use in other loop statements also (like do-enddo loop, while-endwhile)
SY-INDEX is a counter for following loops: do...enddo, while..endwhile
SY-TABIX is a counter for LOOP...ENDLOOP, READ TABLE...
Here is an example from which you can understand the difference between sy-tabix and sy-index.
Itab is an internal table with the following data in it.
id Name
198 XYZ
475 ABC
545 PQR.
loop at itab where id > 300.
write :/ itab-id, itab-name , sy-tabix, sy-index.
endloop.
My output will be :
475 ABC 2 1
545 PQR 3 2
Sy-tabix is the index of the record in internal table.
sy-index gives the no of times of loop passes.
So, for the first record in the output (475 ABC), 2 is the index of the record in internal table and as it is first time loop pass occured, sy-index value is 1.
Regards,
navjot
award points

The difference between chapter markers and dvd studio pro markers

Does anyone know what is the difference between chapter markers and dvd studio pro markers? I can not find anywhere on Google. Also in the tutorials I have seen, suggesting DVD Studio Pro markers, but it did not mention the chapter markers.
Thanks,

"Adding Chapter and Compression Markers to Your Sequence
Once you have your edited sequence or program finished, you can add markers to the sequence for use on DVD. Markers are reference points you can place within clips or sequences that identify specific frames. There are two kinds of markers you can add that directly relate to authoring a DVD—chapter markers and compression markers.
• Chapter markers allow DVD authoring applications to create a navigable chapter list for your exported QuickTime movie. Chapter markers force MPEG keyframes (known as I-frames) at their location, since the DVD specification requires an I-frame at each chapter point.
• Compression markers identify areas of abrupt change and include two types: those that are automatically inserted by Final Cut Pro at all edit points, and those you manually place in the clip or sequence. Like chapter markers, compression markers force I-frames at their location, although in this case it is for better quality encoding, and they are not used to create a chapter list.
Note: When you export a QuickTime movie, you have an option to export various kinds of markers, including compression, chapter, or DVD Studio Pro markers. *When you choose to export DVD Studio Pro markers, Final Cut Pro actually exports chapter markers and all compression markers.* This includes compression markers you set manually, as well as ones created automatically by Final Cut Pro at edit and transition points."
From the Final Cut Pro User Manual.
So, JS was right the first time

The difference between an iphone and an ipod touch?

i want to know if the difference between an iphone and an ipod touch is just that the iphone is like a phone that has internet and is a phone. or what else is it?

The iPhone includes the same as an iPod Touch but also includes a phone, a camera, and a GPS radio.
In addition to having internet access via wi-fi, the iPhone also has internet access via the cellular network, so as long as you have cellular reception with the iPhone, you have access to the internet in addition to having access via an available wi-fi network.

Difference between CREMDM04 Idoc and CREMAS04 Idoc

Similar Messages

Maybe you are looking for