LSMW Vendor Create /Change (XK01/XK02) by IDOC CREAMS05 for CONTACT PERSON

Hi Experts,
Can you Please help me for CONTACT PERSON (create/ change) upload for vendor using the IDOC type CREMAS05.
which structure is appropriate for CONTACT PERSON in CREMAS05
Thanks in advance,
Babumiya Mohammad

okay, this screen is not active in my system. (are you doing retail?)
if it is address data, then it is usually transmitted with the ADR3MAS idocs
this is at least the case for customer contacts.
Edited by: Jürgen L. on Feb 20, 2012 5:13 PM

Similar Messages

Create Outbound extended IDOC for venodr create & change (XK01 & XK02)

Dear all,
My requirement is as below:
I have to populate an extended IDOC of the standard IDOC CREMAS in the following cases.
1. When a new vendor is created from XK01 with classification characterstics value for supplier status as 'YES'.
2. When a vendor is changed by adding a partner function OA in the partner function.
3. We have to purposefully fail the IDOC when the partner function OA is deleted in XK02 transaction.
4. We have to purposefully fail the IDOC when the main vendor is blocked or deleted(XK05 or XK06).
Since i am new to IDOC, i tried many things but its not working.
I tried by the change pointer method for the standard IDOC but it will create the IDOC in all cases which we don't want it should be created only when supplier status is 'YES' and new partner function OA is created.
Regards,
Manjunath

hi,
I know how to extend an IDOC, but my question is after extending an IDOC i have to populate that outbound IDOC only in some cases.that is when a vendor is created with supplier status as YES, when a vendor is changed by adding an partner function.
I want these checks know where to make these checks before creating an outbound IDOC.i want to knaow a common point where i can make these checks like an exit.
i found 1 exit fo all the cases EXIT_SAPMF02K_001 but in this exit we will have the vendor number because it is exit before save.
Now i am looking into the FM 'MASTERIDOC_CREATE_CREMAS' in which we have an exit 'EXIT_SAPLKD01_001'.
Regards,
Manju

LSMW Vendor Change (XK02) by IDOC CREAMS05?

LSMW Vendor Change (XK02) by IDOC
Hi,
I have below queries for LSMW Vendor Change (XK02) by IDOC
I am using idoc type CREMAS05 for vendor creation , Now i want to update (Change) the vendor using the idoc.
1. will the IDOC type CREMAS05 work for vendor change (XK02) also?
2. when i am executing the LSMW with the IDOC type CREMAS05, it is throughing an error Message no. WY181 "Account group in the IDoc is different " "
Diagnosis
A change to the account group of a vendor master record cannot be made automatically.
The vendor with number 2000000148 currently has account group Z001. However, the IDoc contains account group .
Procedure
Change the account group manually to and then try to edit the IDoc
Please help me.
Thanks,
Babumiya Mohammad
<removed by moderator>
Edited by: Thomas Zloch on Feb 17, 2012

Hi Jürgen L.
Thanks for you answer , Now it is working.
Can you Please help me for CONTACT PERSON (create/ change) upload for vendor using the IDOC type CREMAS05.
which structure is appropriate for CONTACT PERSON in CREMAS05
Thanks in advance,
Babumiya Mohammad

I want IDOC for Vendor master updation ( XK01 &XK02 )

Hi
I want to do LSMW in IDOC method for this vendor updation.
So I want IDOC for Vendor master updation ( XK01 & XK02 ).
I want to do both create vendor and change also.
Regards,
Ravi
Edited by: kandukuri ravi on Dec 1, 2008 2:56 PM

Hi,
For Vendor Master using IDoc's for LSMW,Use Message Type = CREMAS and Basic Type = CREMAS05.
For Basic type 01,02,03...05 are versions which includes more fields in basic type so better use latest version.
Hope it will help you.
Regards,
Sudhakar Reddy.A

How can u triger IDOCS wen ever vendor no. changes in XK02 Using BADI's

Hi all
           When ever i change the vendor no.. in XK02,the idoc have to be triggrer using BADI in ECC6.0 version.Pls Any one help me how to create BADI AND IDOC IN ECC6.0.I am new to both IDOCS and BADI.
Given badi name was -- VENDOR_ADD_DATA_BI .
           Where to u have add funtionality whether in BADI or in particulatr Tcode programe name(means Include programe name)
Pls guide me
Thanks

Hi,
I have done something similar but not the exact. My requirement was to send Customers and moreover I didn't make use of the BADI, instead I used events and change pointers.
What you can do is:
1. put the following code (or something similar) inside your BADI (make sure the BADI is fired only for XK02 and not for t.codes XK01, XK03,...)
This program RBDSECRE is same as T.code BD14. The variable w_vendor_number should match with your BADI parametes.
          SUBMIT RBDSECRE WITH SELLIFNR EQ w_vendor_number
                                          WITH MESTYP    EQ 'CREMAS'
                                          WITH LOGSYS    EQ w_logsys_name
                                          WITH nomsg        EQ 'X'
                                          AND RETURN.
2. create a distribution model for the logical systems and the idoc message type in BD64.
Hope this Helps,
Sumant.

Step-by step procedure for INBOUND IDOC (VENDOR CREATE / CHANGE)

Hi ,
Can any body provide me the step-by-step procedure for Inbound IDOCS.
As i'm new to this i need the the clarification between Inbound & outbound idocs.
How can we differentiate both?
where to define outbound & where to define Inbound?
( If possible Please explain me the procedure for Vendor Create through INBOUND IDOCS )
Thanks in advance..

Hi,
Ale Technology is SAPu2019s technology to support distributed yet integrated processes across several SAP systems.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocu2019s definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programu2019s design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocu2019s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
u2022 Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
u2022 IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
u2022 Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
u2022 Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
u2022 Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
u2022 Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
u2022 Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
u2022 Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc u2013 Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch u2013 ALE Service).
u2022 IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
u2022 Basic integrity check: A basic integrity check is performed on the control record.
u2022 Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
u2022 Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc u2013 Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
u2022 IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
u2022 IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function moduleu2019s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

How to use segment ZCRMXIF_PARTNER_SAVE01 in LSMW to Generate/Change BP data using IDOC

Hi Gurus,
I have an requirement to add contact person first name and last name using Relationship kind as '0001' for an BP.
This requirement i need to work with LSMW and generate IDOC for respective changes.
To work with LSMW and IDOC i need to pass data to ZCRMXIF_PARTNER_SAVE01.
Can you all suggest me what are the mandatory fields to be passed to this segment and what are the fields to which i can pass FIRST NAME and LAST NAME of the CONTACT PERSON of the BP.
Please post me your replies in detail iam new to crm i can understand.
Thanks & Regards,
Saravanan Sambandam

Hi Saravanan,
Which method you used.
Regards,
Madhu.

CREATE BIDDER MAIL CONTENT TO BE EDITED -SENTAFTER CONTACT PERSON CREATION

I need to change the content of the mail (containing user-id) which is sent after creation of a contact person in create bidder tab.
please tell me how to do it.

Hi,
Transaction : SE61
Document class : General text
Document name : PARTNER REQUEST ACCEPTED
You can modify the mail text here.
Regards,
Nikhil

Trigger CREMAS change pointer for vendor classification change in XK02/FK02

Hi,
I have a business case where I need to trigger a change pointer of type CREMAS whenever a client modifies vendor classification in transactions FK02/XK02. I realize classificatiion/characteristics have their own change pointer types (CLFMAS, CHRMAS, etc.), but I was wondering if there was a user exit/BADI available for this scenario where I can manually create a change pointer. I need the characteristic data to be part of a custom IDoc type (based off of CREMAS03), and it's no problem to include this data in the custom IDoc, but I need a way to trigger the change pointer if the clients changes vendor characteristic data, and nothing else.
I also went into transaction BD52 for type CREMAS to see if there's another row for classification (CLASSIFY), but couldn't figure out the right object type.
There's a BADI called CACL_VALUE_CHANGE that triggers when vendor classification is changed, where I can generate my change pointer, but it's triggered before the client saves which means I would have a useless change pointer.
Does anyone have any ideas on what my options are? I hope I've elaborated enough
Thanks,
Chris

I figured out a way to do this which was to implement the BDCP_BEFORE_WRITE BADI which allows you to interrogate a change pointer based on an IDoc message type before it's saved to the database. For starters, change pointers for message type CLFMAS must be activated in order for this to work, even though I'm not interested in those eventual IDocs.
In the IF_EX_BDCP_BEFORE_WRITE~FILTER_BDCPV_BEFORE_WRITE method of the BADI implementation, I was able to loop through all of the change pointers about to be created and this is where I was able to obtain the vendor number the classification is being applied to. I actually added another line to the internal table that's changeable in the method for CREMAS and it worked out well.
The only thing that was difficult was to debug this baby. No matter how you set the breakpoint, it just never hits it until I discovered it's called using an UPDATE TASK. I found an unorthodox method to debug this situation on the web which is to force an endless loop before your custom code such as.........
while sy-subrc <> 98.
endwhile.
<custom code here>
Once your process runs, it will be sitting in an endless loop in an update task which you can view in transaction SM50. From here, you can highlight this line then you can click on "Program Session > Program > Debugging" to debug your code. It's not something I was used to, but it allowed me to debug in the end. I would hope there's better ways, but this worked for now.
I hope this helps someone else!
Cheers,
Chris

Need BOR & event which triggers after vendor master change.

Hi all.
Can you pls let me know the BOR & event which triggers after vendor master change. (Xk02). I used tcodes SWELS (evetn trace) , and SWEL and changed vendor adress using XK02. but I could not find any event or BOR in the trace. Pls help me out.
Cheers,
sam.

Hi
when we change the vendor details we dont have the event which is automatically triggered by the system so we create an zbusinessobject as subtype for the vendor(LFA1) as supertype.
and create a new event in that z business object .
change document for the vendor is KRED you can check it in the CDHDR table by giving tcode name.
after finding changedocument object go to SWEC and create a newentry specifying your changedocumentobject name and BO name and event name and click on radiobutton onchange.
and now you can check whether an entry is getting in swels or not when changing the vendoor details.
Thanks.

Create contact person for a Vendor

Hi experts
Someone could explaim the processes of contact person creation.
I replicated the vendor from R/3 and now I need to send a BId to this vendor but the sistem ask for a contact person, so I tried go to transaction Manage business Partner - Employ to Business Partner and tried to create a contact person for this vendor, but when I try to choose a roles for this user no roles is found and is not possible create the user.
Where can I insert the roles to found when creating the user?
Thanks
Nilson

Hi,
Also you dont need to enter any roles while creating the Contact person for a vendor.You just need to enter the employee/user details who will be the contact person for the vendor and after you save all the data ,the CP for the vendor will be created and the system will issue a message "Contact person XXXX for BP yyyyy created".
BR,
Disha.
Do reward points for useful answers.

Auth. obj. controlling options Create - Change of Table Entry for SE11

Hello,
Could someone please guide me to the authorization object/s which controls the options : Create - Change reached by trans. code SE11, Change, Contents (Ctrl + Shift + F10) , Execute (F8), Table Entry, Create - Change.
Thank you in advance for your cooperation.
Best regards.
Reda Khalifa

Hi,
when you execute SE11 authorization object S_DEVELOP was check.
S_DEVELOP has following nodes.
Activity : create,change,display
Package : z,y
Object name : z,y
Object type : type of object i.e domain,table, index etc.
Authorization group ABAP/4 pro : *
now suppose you want to give user authorization for display only then
Activity should have value 03 only.
in future please post your authorization related thread in security forum.
Security
regards,
kaushal

Field "Contact person" in XK01, MK01, FK01.

Hi,
in SPRO "Define Account Groups with Screen Layout (Vendors)" and "Define Screen Layout per Activity (Vendors)" is possible setting the field "Contact person" in "General data" so that the entry
could be:
-Suppress;
-Req. Entry;
-Opt. entry;
-Display.
The field "Contact person" is being configured so that this is a "Required entry" , but nothing doesn't appear in Vendor master.
How activating this field?
Best regards

Dear sap,
Please try this, go to MK02, enter a vendor with acc.group that you set, is there "contact person" selection under General data tab? if yes , try to change the data for contact person and when you clear the value,then the required mark will show up.Then when you create a vendor using MK01 with ref to the acc.group , then system supposed to prompt the contact person tab to be filled.
Regards,
w1n

Contact Person Integration for Vendor Master(ECC to CRM)

Hi,
Just wanted to know if Contact Persons in Vendor Master records in ERP are replicated in standard to CRM in the object VENDOR_MAIN. Dont seem to find any std. documents on this that says it should be replicated?. Any ideas?.
Thanks.
Example:
Go to Tx: xk01 in ERP and maintain a Contact person.Replicate to CRM.Vendor is created as an Organization but no relatonship is created to a Contact Person.Is this a std behaviour?.
Regards,
Praveen

Hi,
The answer as far as I've known so far is that this scenario is not available in standard.
An idea would be to use a new adapter object in CRM. (on a project basis.)
Regards,
Praveen

How to change Number range to Contact Person in Customer Master Record

Dear all,
We are maintaining contact person details under contact person tab in customer master record.
Currently contact person is being created using VAP1 transaction.
Can we automate this contact person creation by entering the data in contact person itself?
and where can we change the number range of contact person.
I have searched a lot to find the solution for this. Please help me to resolve this issue. Your suggestions will be highly appreciated.
Best regards
Venkat

Hi Venkat,
To your first question: "Can we automate this contact person creation by entering the data in contact person itself?"
Yes, you can enter the contact person directly in the customer master in the contact person tab. A number is generated automatically.
To your second question, go to transaction SNUM, and there use object "PARTNER". Here you can configure number range for contact persons.
Hope this helps,
Regards
Nikhilesh

LSMW Vendor Create /Change (XK01/XK02) by IDOC CREAMS05 for CONTACT PERSON

Similar Messages

Maybe you are looking for