Business Partner Transfer using ALE/IDOCS
Dear Gurus,
I am using S.R.M. 5.0 system. I am encountering scenario of transferring the business partners from S.R.M sytem to C project which is again add-on module provided by SAP. I have created Distribution Model and have assigned the message type BUS1006 (message type for Business Partner). But I am not able to find the transaction to send the data across to CPD system like BD10 is for transferring material in R/3 system.I have also observerd that the dala eleement of the business partner has got change pointer attached to it. I have got two questions.
1. Is the method that I followed is correct to transfer data? I did it by seeing PPT .If yes than what is the t-code to transfer the business partner equivalent to BD10.
2. In case of change pointers begin activated how should I transfer data? if any documentation is there that will be helpful?
Thanks and Regards,
Saurabh Chhatre
Thanks and Regards,
Saurabh Chhatre
Hi Sergio,
When I tried BUPA_SEND , I came across another transaction BUPA_CALL_FU.
This transaction allows us to select function modules that needs to be called for sending the business partner from S.R.M 5.0.Have you got any idea which are the mandatory F.M's that needs to be selected. I am asking this because there are few F.M's which do not exist in the system.
Or have do you have any idea how we can create these F.M's. As these are standard I am thinking it must be done through customization.
Thanks in advance
Thanks and Regards,
Saurabh Chhatre
Similar Messages
-
Data transfer using ALE/IDOC into XML.
Dear All,
I have to transfer FI document data (FB01) from the sap system ,convert it into XML and dump it in 1 of the file servers.I want to do this using ALE/IDOC.Is it possible to do the same and how.Similarly i want to do the same for Vendor and Customer master i.e sending the data in XML format.
Kindly Suggest how do i go about doin the same..Its very urgent.Please help.
Thanks & Regards,
Lailu Philip.In continuation:
Example Purchasing & Selling scenario
We will develop a custom IDoc to carry the billing number from the Service Receivers system to the Service Providers system. We will populate the IDoc in a user exit on the sending side and we will process the transaction on the receiving side using a custom function module and a BDC transaction call.
No rule conversion, segment filtering or version conversion will be implemented in the model as described in Figure 1.
Requirements
Working ALE environment - See ALE Basis Configuration Guide;
ALE scenario design together with the business requirement;
Development access; and
ALE configuration access.
NOTES:
1. All IMG references to transactions are located in the transaction SALE which is the ALE portion of the IMG
2. This is one way of developing a scenario where no message control exists. If message control exist (EG. On purchase orders) then NAST can be used to call an outbound function module that would create the required IDocs.
3. Extensive knowledge of IDocs and ALE basis configuration is required in order to understand this guide.
2. OUTBOUND PROCESSING
2.1. Create IDoc type (WE30) Client independent
The IDoc type refers to the IDoc structure that you will require for your development. In our case the IDoc type is called ZINVRV01. This IDoc type will have 1 segment called Z1INVRV with 2 fields, LIFNR & XBLNR, in this segment. If you require many segments or nested segments then they are also created using the same procedure.
We will create the IDoc of the following structure:
ZINVRV01
Purchasing and Selling - Invoice receipt reversal
Z1INVRV P&S - Segment 1
Segment fields
LIFNR Vendor account number
XBLNR Reference document number
Figure 3: IDoc type ZINVRV01
To create the IDoc type, follow these next few steps:
Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
Type in ZINVRV01 and click on Basic IDoc type, click the Create icon
Click on Create new (we are creating an IDoc from scratch but you may want to copy another IDoc if it is similar to your requirements) and enter a description, and press enter
Click on ZINVRV01 and then on the Create icon
Enter Z1INVRV as the segment type (must start with Z1), check mandatory if the segment must exist (in this case check it), enter 1 in minimum number and 1 as maximum number. (Make the maximum number 9999999999 if there are going to be many of these segments in each IDoc. IE. When line items are passed via IDocs), click on Segment editor
Enter a description for your segment type and create
Enter a description for your segment, enter each field required in your IDoc, in our case type LIFNR across for Field name, DE structure and DE documentation, repeat for XBLNR and press enter to validate.
Save and generate, press back
To release the segment choose Goto, Release from the menu
Check the box on the line of your new segment
Save, back and enter
Your IDoc type structure should be displayed with your new segment
Save and back
To release the IDoc type choose Extras, Release type from the menu and Yes
Your IDoc is now ready for use. If you need to add fields or segments to your IDoc type, you will need to cancel the release of the IDoc type as well as the segment release using a similar procedure followed above (except now you uncheck the release box for the segment and you choose cancel release for the IDoc type).
2.2. Create message type (WE81) Client independent
To create a new message type, follow these next few steps:
Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
Choose Create logical message type by double clicking on it
Click on change icon to enter change mode
Click on New entries to add a new type
Enter the required message type, in our case it is ZINVRV and an appropriate description
Save and exit.
Your message type has now been created. The next step will be to link it to the IDoc.
2.2.1. Link message to IDoc type (WE82 & BD69) Client independent
To link the message type to the IDoc type follow these next few steps:
Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
2.2.2. Maintain object type for message type (BD59) Client independent
The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
For our own message type and IDoc you must maintain object types for the links.
If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
To add an object type to our message type, follow these next few steps:
Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
Type in your message type ZINVRV and press enter
Click on New entries
Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
Save and exit.
You have now created an object that well use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
We now need to add our new message type to the distribution model.
2.3. Configuring the Distribution Model
This task is performed on your ALE reference client.
2.3.1. Manual Configuration (BD64) Client dependent
To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
Choose the receiving systems to which the sending system must forward message type ZINVRV to.
For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
Save the entries.
NOTES:
You cannot maintain a message type between the same sender and receiver in more than one customer distribution model.
Only the owner is authorised to modify the model.
To change the owner of a model, choose the 'Maintain ownership of customer distribution model' function. Make sure that all changes will be distributed to all systems that know the corresponding model. To do so, you can use the correction and transport system.
To transport the customer distribution model you should use the Distribute customer model function of the IMG as described below.
2.3.2. Distribute customer model (BD71) Client dependent
After the customer model has been created centrally, it must be distributed to the other remote systems. This entails first of all setting up the communication for the distributed systems and then sending the model.
2.3.2.1. Distribute Model (BD71) Client dependent
This task is performed on your ALE reference client. To distribute the customer distribution model, read the ALE configuration procedure and follow these steps:
Make the settings for the communication with the other decentral systems, you have not set them yet.
Define the RFC destination for R/3 connections whose names correspond to the name of the corresponding logical system.
Create the output partner profile.
Distribute the customer model
Specify the name of the customer model.
You must specify the target system to which you want to distribute the customer model.
You must repeat this function for every distributed logical system.
2.3.2.2. Maintain sending system partner profile (WE20) Client dependent
With this function, you define the partner profiles for all outbound and inbound messages on the basis of the customer distribution model.
After you have defined and distributed the customer model, you will have to maintain the partner profiles locally. To do this read the ALE configuration procedure.
Enter the output mode (background, immediately) and the package size for outbound processing.
Requirements
The customer model must be maintained.
RFC destinations must be maintained.
The customer model must be distributed.
To ensure that the appropriate persons in charge are informed if a processing error occurs, you must make settings in: Error processing Maintain organisational units.
2.4. Populate & distribute IDoc using ABAP
An IDoc consists of a control record with structure edidc and one or more data records with structure edidd. The control record contains the sender and recipient of the IDoc, as well as information on the type of message.
To be able to pass an IDoc to the ALE layer, you must set up a field string with structure edidc and an internal table with structure edidd. They are used to call function module master_idoc_distribute, which performs the save to the database and triggers the dispatch if necessary.
2.4.1. Example code
The code displayed below does the following:
populates our IDoc segment Z1INVR with the 2 fields XBLNR and LIFNR, populates the segment name and appends this to an internal table used to store the IDoc data;
populates the control record info with the message type and IDoc type; and
calls the MASTER_IDOC_DISTRIBUTE function module which distributes the IDoc as configured in the customer distribution model.
Data declaration statements
DATA: C_INVREV_SEGNAME(7) TYPE C VALUE 'Z1INVRV',
C_INVREV_MESTYPE(6) TYPE C VALUE 'ZINVRV',
C_INVREV_IDOC_TYPE(8) TYPE C VALUE 'ZINVRV01',
Z1INVRV LIKE Z1INVRV,
C_INVREV_DOCTYPE LIKE BKPF-BLART VALUE 'YY',
IDOC_CONTROL LIKE EDIDC,
T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE.
Move the document header into a structure
LOOP AT DOC_HEAD_TAB INTO DOC_HEAD.
ENDLOOP.
Move the document item data into a structure
LOOP AT DOC_ITEM_TAB INTO DOC_ITEM WHERE NOT ( LIFNR IS INITIAL ).
ENDLOOP.
Populate the IDoc segments field with the required data
CLEAR Z1INVRV.
Z1INVRV-LIFNR = DOC_ITEM-LIFNR. Store vendor number for filter
Z1INVRV-XBLNR = DOC_HEAD-XBLNR. Billing number
IDOC_DATA-SEGNAM = C_INVREV_SEGNAME. Segment name
IDOC_DATA-SDATA = Z1INVRV. Segment data
APPEND IDOC_DATA. Populate IDoc internal table
Move the control data info required for the distribution
IDOC_CONTROL-MESTYP = C_INVREV_MESTYPE.
IDOC_CONTROL-DOCTYP = C_INVREV_IDOC_TYPE.
Call the distribute function with the required parameters
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' IN UPDATE TASK
EXPORTING
MASTER_IDOC_CONTROL = IDOC_CONTROL
TABLES
COMMUNICATION_IDOC_CONTROL = T_COMM_CONTROL
MASTER_IDOC_DATA = IDOC_DATA
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5.
Figure 4: Outbound processing example code
NOTE:
For debugging purposes, use transaction WE05 (IDoc overview) to see check your IDoc status, or to see whether an IDoc was created/
3. INBOUND PROCESSING
3.1. Create Function Module
This function module is called when a message type, of type ZINVRV, comes into the receiving system. This needs to be configured and is dealt with later in this section. The function module is passed the IDoc as a parameter.
Example parameters
Import parameters Reference field Opt Y/N
INPUT_METHOD BDWFAP_PAR-INPUTMETHD N
MASS_PROCESSING BDWFAP_PAR-MASS_PROC N
Export Parameters Reference field Opt Y/N
WORKFLOW_RESULT BDWFAP_PAR-RESULT N
APPLICATION_VARIABLE BDWFAP_PAR-APPL_VAR N
IN_UPDATE_TASK BDWFAP_PAR-UPDATETASK N
CALL_TRANSACTION_DONE BDWFAP_PAR-CALLTRANS N
Table Parameters Reference field Optional Y/N
IDOC_CONTRL EDIDC
IDOC_DATA EDIDD
IDOC_STATUS BDIDOCSTAT
RETURN_VARIABLES BDWFRETVAR
SERIALIZATION_INFO BDI_SER
Exceptions
WRONG_FUNCTION_CALLED
Example code
The code displayed below does the following:
populates a BDC table with the IDoc info;
calls the transaction via a BDC call; and
updates the IDoc status according to the BDC error status.
EXTRACT FROM: Z_IDOC_INPUT_ZINVRV
Declaration of local variables
DATA: C_SEGNAM(10) TYPE C VALUE 'Z1INVRV'.
*-Loop through the IDOCs
LOOP AT IDOC_CONTRL.
*---Loop through the data for the IDOC
LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.
CASE IDOC_DATA-SEGNAM.
WHEN C_SEGNAM.
Here we get the info from the idoc table
IT_Z1INVRV = IDOC_DATA-SDATA.
ENDCASE.
PERFORM REV_INV.
ENDLOOP.
PERFORM UPDATE_IDOC_STATUS.
ENDLOOP.
FORM REV_INV "Reverse invoice form
Local variables & constants
DATA: C_TCODE LIKE BKPF-TCODE VALUE 'VF11'. "BDC transaction code
Now we can build the bdc table to call the reversal transaction start of screen 109
CLEAR BDC_TAB.
BDC_TAB-PROGRAM = 'SAPMV60A'.
BDC_TAB-DYNPRO = '109'.
BDC_TAB-DYNBEGIN = 'X'.
APPEND BDC_TAB.
Document number
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'KOMFK-VBELN(01)'.
BDC_TAB-FVAL = IT_Z1INVRV-XBLNR. "Billing document number
APPEND BDC_TAB.
OK Code for screen 109
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'BDC_OKCODE'.
BDC_TAB-FVAL = 'SICH'.
APPEND BDC_TAB.
Now we can call transaction 'VF11' with the populated bdc table. The transaction is called inside the idoc-contrl loop, so a transaction will be called for every idoc (journal). the transaction is called in no-display mode ('N') because this code runs in background as it is called by ale. The update is specified to be synchronous ('S') because we have to wait for the result to update the idoc status correctly.
CALL TRANSACTION C_TCODE USING BDC_TAB MODE 'N' UPDATE 'S'.
Store the return code for use in another form (status update)
RETURN_CODE = SY-SUBRC.
Here we check the return code, if there was an error, we put the transaction in a bdc session for the user to review and correct.
IF SY-SUBRC NE 0.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
CLIENT = SY-MANDT
GROUP = 'ZINVRV'
USER = C_ALE_USER
KEEP = 'X'.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
TCODE = C_TCODE
TABLES
DYNPROTAB = BDC_TAB.
CALL FUNCTION 'BDC_CLOSE_GROUP'
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
ELSE. "No problems
C_EXISTS = 'N'.
Select from the billing document table to get sales doc number
SELECT * FROM VBRP WHERE VBELN = IT_Z1INVRV-XBLNR.
Select from the sales document table to get user status number
SELECT SINGLE * FROM VBAP WHERE VBELN = VBRP-AUBEL AND
POSNR = VBRP-AUPOS.
Select from the status table to change the user status to pending
SELECT * FROM JEST WHERE OBJNR = VBAP-OBJNR AND
STAT LIKE C_USER_STATUS.
IF JEST-STAT = C_US_PENDING. "User status is pending
JEST-INACT = C_UNCHECKED. "Make pending the active status
UPDATE JEST.
C_EXISTS = 'Y'. "I.E. An entry is already in table
ELSEIF JEST-INACT = C_UNCHECKED AND JEST-STAT NE C_US_PENDING.
JEST-INACT = C_CHECKED. "Make everything else inactive
UPDATE JEST.
ENDIF.
ENDSELECT.
IF C_EXISTS = 'N'. "I.E. Pending has never been a status before
JEST-OBJNR = VBAP-OBJNR.
JEST-STAT = C_US_PENDING.
JEST-INACT = C_UNCHECKED. "Make pending the active status
INSERT JEST.
ENDIF.
ENDSELECT. "Select from VBRP (Billing document table)
ENDIF.
ENDFORM. " REV_INV
FORM UPDATE_IDOC_STATUS.
Now we check the CALL TRANSACTION return code and set IDOC status
CLEAR IDOC_STATUS.
IF RETURN_CODE = 0.
WORKFLOW_RESULT = '0'.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-STATUS = '53'.
IDOC_STATUS-UNAME = SY-UNAME.
IDOC_STATUS-REPID = SY-REPID.
IDOC_STATUS-MSGTY = SY-MSGTY.
IDOC_STATUS-MSGID = SY-MSGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
ELSE.
WORKFLOW_RESULT = '99999'.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-STATUS = '51'.
IDOC_STATUS-UNAME = SY-UNAME.
IDOC_STATUS-REPID = SY-REPID.
IDOC_STATUS-MSGTY = SY-MSGTY.
IDOC_STATUS-MSGID = SY-MSGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
RETURN_VARIABLES-WF_PARAM = 'ERROR_IDOCS'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
ENDIF.
APPEND IDOC_STATUS.
ENDFORM. " UPDATE_IDOC_STATUS
Figure 5: Inbound processing example code
3.1.1. Debugging inbound FM
Use transaction WE19 to test inbound function module in debugging mode. Also use WE05 to view the IDocs and their statuses.
3.2. Maintain ALE attributes
The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.
3.2.1. Link Message Type to Function Module (WE57) Client independent
To link a message (ZINVRV) type to a function module (Z_IDOC_INPUT_ZINVRV) follow these steps:
Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)
Select an entry (EG. IDOC_INPUT_ORDERS) and copy
Type in module name Z_IDOC_INPUT_ZINVRV
Type in basic IDoc type as ZINVRV01
Type in message type as ZINVRV
Type object type as IDOCINVOIC (Invoice document) - Used for workflow
Direction should be set to 2 for inbound
Enter and save
3.2.2. Define FM settings (BD51) Client independent
Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)
Click on New entries
Type in the name of the new function module Z_IDOC_INPUT_ZINVRV
Enter 0 for mass processing in the output column
Save and Exit
3.2.3. Maintain process codes (WE42) Client dependent
A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.
To maintain the process code follow these steps:
Log on to the appropriate receiving system client
Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)
Choose Inbound with ALE service
Choose Processing with function module
Click on Processing with function module and choose create icon
Click on New Entries
Type in process code ZINR and give it a description and save
Now you are asked to Please maintain codes added in ALE entry methods, enter and choose Z_IDOC_INPUT_FIRVSL and copy it. You should choose a FM similar to your one.
Enter your process code ZINR
Enter your function module Z_IDOC_INPUT_ZINVRV
NOTE: The next 6 steps are used in workflow error handling.
Enter IDPKFIDCMT in object type
Enter MASSINPUTFINISHED in End event
Enter IDOCINVOIC in IDoc object type
Enter INPUTERROROCCURREDFI in IDoc start event
Enter INPUTFINISHEDFI in IDoc End event
Enter IDOCINVOIC in Application object type
You will need to determine the task associated with object IDOCINVOIC, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.
To set up the workflow area please consult the Workflow config guide.
3.3. Create inbound partner profile
For each message type you need to maintain the inbound partner profiles.
3.3.1. Maintain receiving system partner profile (WE20) Client dependent
To maintain inbound partner profiles read the document ALE configuration procedure:
Add the message type ZINVRV with process code ZINR.
Enter the output mode (background, immediately) for inbound processing and NO message code.
Enter the position S and choose the ALE administrator 50000085. This position will then receive all the technical ALE errors via workflow.
3.4. Test
Once the inbound function module has been debugged the scenario should be ready to test in its entirety. If problems occur, read through the relevant areas of this document to check your configuration or code.
Hope this will help you,
If you want me to explain more, you can give me your email id.
Reward with points incase you are satisfied.
Regards,
Sushama -
Business Partner Conversion using LSMW IDOC
Hi Experts,
I need a serious suggestion.
I am planning to do my Business Partner master data conversions using LSMW method IDOC CRMXIF_PARTNER_SAVE_M03. Is this is right choice or best practice?
During Coversions how do we do error handling or reporting. For example i have uploaded 10k BP's. if there 1k errors how do you report. I think it is tough to check each and every idoc status and message.
Thanks guys.Hi Experts,
I need a serious suggestion.
I am planning to do my Business Partner master data conversions using LSMW method IDOC CRMXIF_PARTNER_SAVE_M03. Is this is right choice or best practice?
During Coversions how do we do error handling or reporting. For example i have uploaded 10k BP's. if there 1k errors how do you report. I think it is tough to check each and every idoc status and message.
Thanks guys. -
Data Transfer Using ALE/IDOC
Dear All,
I have to implement an ALE\IDOC scenario and i am totally new to this.I have a web based software from where i need to pull data into SAP.
The moment billing takes place in my web based software i have to pull the required data and generate an accounting document number in SAP using transactions FB01 er FB60 and FB70 depending on vendor or customer Invoice which means i need to have my vendor and customer master data in place before this.The IDOC which i would be using is FIDCCP01.My question is:
The web based software can generate both an XML and EDI file into a domain from where SAP can fetch it. Now,
1. If they can generate an EDI file which format should it be in?
2.If EDI file generation is possible through that web based software its structure should be exactly the same as my IDOC structure right?
3. What would then be the process on SAP side to pick that EDI file data?
4. Does the transaction WE16 help in picking up an XML file format or an EDI format and convert it automatically into an IDOC and how do we go about it?
5. Now when this idoc is going to generate accounting documents against those billing documents if the customer or vendor does not exist is there a way by which i can first create this vendor\customer in the master and then continue using some other abap tool?
6. Could an email be generated automatically when teh document is posted?
I know these are a lot of questions but i really need an answer to this.
If u have an answer my alternate email id is [email protected]
Awaiting your reply shortly.
Thanks & Regards,
Lailu Philip.1. XML Format
2. Message type INVOIC01 or INVOIC02 format
3. You need to write a Z program to read data from that path and use FM IDOC_XML_FROM_FILE to convert that XML file to IDOC.
4. Use transaction we60 with above message type it will all help you need. we16 is for testing it could not be used for a solution.
5. In your Z program check before the XML is ubmitted for processing whether the customer exist by select on KNA1 if not use FM BAPI_CUSTOMER_CREATE to create and same for vendor.
6. You need to implement workflow for this.....
Reward points it this helps -
Business partner migration using lsmw direct load .
Hi,
We need to do business partner migration using the direct load method.
We are thinking of using direct input method of lsmw for the data transfer.
Could someone suggest a proper object/ subobject for the same.
Alternatively has anyone done the same using LSMWbapi or LSMWidocs.
Inputs will be highly appreciated <<text removed>>
Dirk.
Edited by: Matt on Dec 19, 2008 1:33 PM - Do not offer rewards. Please read the rules of engagement.Hi ,
Does this solution give any way to update the customer fields too ?
We have few customer fields added to BUT tables ... How can we update these fields using LSMW and IDOC ?
Could you please give your opinion on thesame. -
Issue in transporting changed material type using ALE-IDOC
Hi All,
I am sending the material master data from one system to another using ALE-IDOC.The issue is that teh material type is not getting sent from one system to another after changing the material type.I mean the changes in material type are not getting updated.I will be indeed thankful if anyone can guide me resolve this issue.
Thanks.Hi,
Not all the fields that are changed in material master are sent in the Idoc. Material type is one such field.
Create change pointer on some other field ex. net value or material desc. and transfer the material type changes under it.
KR Jaideep, -
Lsmw using ALE/IDOC Method
Hi Team,
I am trying for lsmw using ALE/IDOC Method.
I have defined the segment type, message type, defined a basic type and defined a partner profile of the receiver system.
When i try to execute the Start Idoc Generation step in generating LSMW creation steps. I am getting below error "No partner exists with the nae ", type".
Please help me in resolving the warining.
No partner exists with the name '', type ''
Regards
Sunil
Edited by: sunil kumar on Jul 30, 2009 11:26 AMHi,
for LSMW , you have to create partner profile type as 'US'.
once the partner profile created in we20,
goto tcode lsmw , in menu select "Settings -> Inbound Idoc Processing"
maintain FilePort, partner type and Partner number and then press Activiate Idoc Inbound pricessing.
Then you will not get this error message.
Regards,
Bhavana -
Upload CRM activity using ALE IDOC
Hi All,
I am uploading the crm activity using ale idoc in lsmw , i mapped the partner information in to segments and passing value to the fields but it is not getting values , please give what may be th problem.
Regards,
Naveenanswered
-
Help: one request using ALE&IDOC to Posting Goods Issue about MaterialScrap
Hi Exports,
i got a situation. My client is using ALE&IDOC to deal with the Material Scrapping. The business scenario is:
1. One third system (Non-SAP) Send IDOC to SAP Production Server through the Intermedia SEEBEYOND.
Message Type: MBGMCR
IDOC Type: MBGMCR02
BUSINESS OBJECT: BUS2017
2. SAP Production Server use "Message Type: MBGMCR" to find out the BAPI in Distribution Model and trigger the BAPI.
the Distribution Model:
Model View
SEEBEYONG
PRODUCTION
GoodsMovement.CreateFromData
Reciever determination: no filter
Now my client's request is:
When the Movement Type is 551 in the IDOC Segment "E1BP2017_GM_ITEM_CREATE", This IDOC will be ignore and not trigger the BAPI to post goods issue.
i try to add the destination filter in the Distribution Model. but when i add the filter group, there are only two filter parameter ("Plant" and "Storage Location") and don't allow to add others.
i have no idea now. can anyone give me a favor. thank you very much in advance.
Edited by: Dave Wang on Feb 29, 2008 7:09 AMWe got hold of the Idoc type 'DELVRY03 PGI SHPCON' we are able to post the Idoc but we are able to do the packing only or we are able to change the deliveries but the PGI is not happening..
please help us on this.. is there some condig that updates the delivery with the PGi or is there something else do be done in the Idoc....
will provide additional details if required.
Thanks
Arun -
How to do search of business partner data, using a message from external sy
Hi CRM Gems,
please send the answer to the following question.
1.How to do search of business partner data, using a message from external system. What FMs, BAPI etc that can be used for this functionality?
your answer will be valuble to me.
Regards,
Krishna..Hi krishna,
Look at BAPI BAPI_BUPA_SEARCH.
Regards.
Manuel -
Passing Changed extended fields using ALE-IDOC to receiving system
Hi all,
Please tell me how passing changed extended fields using ALE-IDOC to receiving system can be achieved. Is it possible by Chnage pointer concept.Do i need to do some coading after data enters into receiving system as it is required while creating the entries in database table.
For ex. in matmas05 extended for classification and inspection view and then created using 'CREATION'
related bapi.Do i also need to incorporate the changes by change related bapi or ir can be handled by change pointer concept.
Thanks.Hi Sanu
1) Please tell me how passing changed extended fields using ALE-IDOC to receiving system can be achieved. Is it possible by Chnage pointer concept.
=> Looks like you have extended standard IDOC here. so you need to find User Exit or BADI for the Push program to populate the additional fields. Yes, it is possible thru change pointers as well.
1) Do i need to do some coading after data enters into receiving system as it is required while creating the entries in database table.
=> Yes, as suggested in 1 try finding User Exits/BADIs.
Regards
Shital -
Enhancement of Business Partner (Relationships) using BDT -Bus Data Toolset
Dear Experts,
I have a requirement from my customer enhancing the Business Partner Relationships using BDT.
I should add 2 fields namely salary, employer start date in the Business partner Relationships, it must be added in the characteristics of relationships as one employee can have multiple employers and vice versa.
If I would like to add the fields in Business Relationships using BDT, are the steps same as adding fields in business partner? or do we need to perform any other steps? Did someone already did this type of modification, please provide your suggestions.
After adding the fields is it possible to cusomize the fields for history of the changes? e.g. if salary field has been newly added and after creating a BP after some days I want to change the salary and for the changed salary I want to have a history.
I would appreciate if you can help me with your suggestions.
Many thanks and best regards,
AfrozSolved the problem Using EEWB.
-
Problem in creating Invoice receipt using ALE-IDoc?
Hi all,
I implemented the auto creation of invoice receipt when billing document created using ALE-Idoc. It is working fine in PRD also.
But today , there occurred a problem in this . The problem is when the billing document is created the Invoice receipt is not creating directly , but a job is creating. But till yesterday it created the invoice receipt immediately as we required.
So please help me on changing the creation of invoice receipt directly from current job creation?
No configuration has been changed , but my user tried to create the more than one billing document at a time.so i think this is the reason for it. But now though he is creating only one billing document , it is creating a job.
Please reply ASAP.
Thanks,
Vamshi.Solved .
-
Integrating SAP CRM with the SAP HR module using ALE/IDOC
Hi,
We replicated HR data(employee and position) from SAP HR to SAP CRM system using ALE/IDOC.
Here I have one question,If I change the position to the employee in CRM system,will changes happen in SAP HR system automatically? or Delta changes will haapen? If yes pl explain.
Using change pointers master data changes flowsfrom SAP HR to SAP CRM .
TIA.
PV.Hi
To integrate... between those systems
first of all u have to create message type to tose fields with t code bd52.
then activate that massege type in bd50.
and after that one u have to activate chaneg pointers globally with bd61.
if u did these thigns if u made any chnegs to those fileds that witll be reflected in the next system
Regards,
Prasad. -
How to Remove Business Partner Address using DI Server
Hello,
I need to remove Business Partner Addresses using DI Server, the example in the SDK only mentions the remove of the entire business partner, but I need to delete only one of the business partner addresses, how can it be done?Hi,
the usage of the "UpdateWithSubDeletion" method of B1 object atom might be an option.
You need to update the complete business Partner with the changed amount of addresses.
The usage is tricky, you need to retrieve the BP, which you want to update, first via synchronous retrieval method using import/export mode.
From the retrieval result you should start to update every segment with all fields including the BPAddresses segment in exactly the same sorting order as displayed from the synchronous retrieval.
Best regards
Bastian
Maybe you are looking for
-
Can I set kerning differently in one sentence?
Can I set kerning differently in one sentence? I have to make it in javascript. help me please. function enterEanCode(){ var EanText= groupRef.textFrames.add(); EanText.textRange.size = 20.74; EanText.textRange.character
-
I want to insert local time & date in my site
Wednesday 25 May 2008 | 13:01 GMT+2 | Cyprus-EU I want to insert local time & date in my site , well zone is GMT+2 , below is correct for date , what about time ? [CODE]<script language="JavaScript" type="text/javascript"><!-- var months = new Array(
-
TIPS(20) : MAKE A MAP OF YOUR ORACLE FILES
제품 : SQL*PLUS 작성날짜 : 1996-11-12 TIPS(20) : Make a Map of Your Oracle Files ========================================== The script below generates a report on all the Oracle files (database, redo log, and control) in an Oracle UNIX system. It's like a
-
Exit from ABAP FPM application to anothor WD application (W/O FPM)
Hi Experts, I am working on a custom ABAP FPM application using roadmap pattern. I have anothor WD application w/o FPM application which calls my second FPM application. I do the navigation from my first application to FPM application using an exit p
-
ICal does not update status when someone accepts my invitation
If I send a meeting request out from iCal, and someone accepts, their status in iCal does not change, i.e. in the event, the icon against their name remains as a grey question mark and does not change to a green tick. This is annoying because of cour