IDOC type CRMXIF_ORDER_SAVE_M in CRM thru LSMW to create Service Contracts.

Hi All,
I am trying to create Service contracts using IDOC type CRMXIF_ORDER_SAVE_M in CRM thru LSMW.
I have a mapping issue of the file fields to the segment fields;
I have 5 files, Contract Header, Items, Dates, Partners, Objects(Serial numbers);
I Appreciate if you send me the mapping details for me if some one has already done this please;
or any otherhelp on the notes/documents are highly appreciated
Thanks
Iver

hi, do you mean the problem is in the file resource file, and you want to use it in LSMW?
If so, I have meet the similar problem, two source file inbound into LSMW. one header , one item
And I solve it in this way,
combine the 2 file before lsmw read it, like this
Header data 1 /   item1
header data 1 /   item2
header data 2 /   item1
header data 3 /   item1
header data 3 /   item2
for each line, the header data is exist, if item is mutiple, the header line can be repeat.
Then the 2 file combine to one file, lsmw read the combined file
You need to do some additional logic in data mapping, mapping the different item in each loop, but header data once if they are same.

Similar Messages

User,Customer exits or BADI for IDOC Type - CRMXIF_ORDER_SAVE_M01 in CRM

Hi Friends,
We are creating teh EDI Sales order in CRM using below details:
Basic Type - CRMXIF_ORDER_SAVE_M01
Message Type - CRMXIF_ORDER_SAVE_M
Functional Module - IDOC_INPUT_CRMXIF_ORDER_SAVE_M
Direction -Inbound
We need to customize the values for the IDOC,
Can any one help us in providing the details on any Customer Exits , User Exits and /or BADIs for the abov ementioned FM.
We greatly appreciate your early responce.
Thanks
Vijay

Thanks Naresh, it helped...
Can you please help on the below:
1. For outbound Sales order IDoc- CRMXIF_ORDER_SAVE_M01,need BADIs for modification of the IDoc before it gets generated.
2. Need program to generate output as outbound IDoc- CRMXIF_ORDER_SAVE_M01 for sales order conformation/acknowledgement.
3. Need a BADI after the EDI Sales order is saved.
Thanks in advance
Vijay

Has anyone ever process an IDOC type ORDERS05 in CRM?

I'm just trying to determine whether I'm onto a loss-leader here, or not.
Regards
Gary

Hi David,
I cannot see anything immediately that points to your problem however maybe the following helps.
1. Your modify/save procedure is not clear from the text. You should only use the BOL modify/save/committ commands and never the ABAP Commit statement directly.
You could try and do a general save as follows:
data: bol_core type ref to cl_crm_bol_core.
bol_core ?= cl_crm_bol_core=>get_instance( ).
bol_core->modify( ).
An end contact should handle the commit for you. if the problem persists you could also debug the save_objects and modify_objects methods of class CL_CRM_APPL_INTLAY_IBASE_NEW. Hope this helps.
Kind regards,
Jared Gibson

Which IDOC segments need to be filled for message type CRMXIF_ORDER_SAVE_M

Hi ,
I am working on data migration to CRM7.0 system.I am using LSMW for creating ISU Contracts using CRMXIF_ORDER_SAVE_M message type and CRMXIF_ORDER_SAVE_M01 IDOC kindly help me in what all segments needs to be filled for creating ISU contract in CRM system.
Kindly share if there are any documents related to data migration into CRM system for IS - Utilities.I need to migrate u201CBusiness Partnersu201D, u201DISU Contract Accountsu201D, u201DConnection Objectsu201D, u201DPODu201D & u201CContractsu201D to CRM 7.0 .
Also I need to migrate Customer Interaction Records, Business Activities, Service requests and other information such as u201CProspectsu201D, u201CMarketing Attributesu201D to CRM 7.0.
Kindly help me in this as I am not able to find any thing from web.
Regards,
Suresh.

Hello,
I'm not sure you're taking the best approch.
Usually when you need to migrate ISU contracts into an ISU-CRM integrated system, you first migrate everything you need in ISU through the VERY powerful migration workbench available (transaction code EMIGALL), and then you replicate your data to CRM via INITIAL download.
That's definitely the strategy that will give you the best performance, and less work.
Kind regards,
Nicolas Busson.

IDoc type could not be determined for the IDoc in F110

Dear All,
The below mentioned error is encountered by us in F110.We have check all the setiing and not able to find the solution for this error.
Now our heads has gone for a toss....can anyone kindly suggest what and where we have missed out.
The system is not creating the IDOC file.....
IDoc type could not be determined for the IDoc
Message no. B1090
Diagnosis
The IDoc passed to the ALE layer could not be processed. The specifications passed in the control record were not correct.
The basic IDoc type (field EDIDC-IDOCTP on the outbound side or EDI_DC-IDOCTYP on the inbound side)has not been specified for this IDoc.
The attempt to read the basic IDoc type from table EDIDO also failed. No table entry was found for IDoc type from field DOCTYP.
Procedure
Possible error sources:
- The calling program did not provide values for the fields specified above correctly. Make a note of the transaction in which this error occurred and consult your ALE administrator.
- The IDoc type is not known in your system and must be maintained.
Kindly do the needful.
Regards

If you want to create IDocs from the proposal run, outbound parameters (we20) with the 'Test' flag are required in addition.
see OSS note 504230 : Message EUPEXR forms the logical unit around the individual payment messages (PAYEXT IDocs). The E1IDRD1 segments contain the IDoc numbers of the payment messages in field DOCNUM. Segment E1IDRS1 contains check sums (total of all amounts, account numbers, bank numbers, number of payment messages). This information is provided for the EDI subsystem. Set up EUPEXR In Transaction WE20 for the partner profile for the house bank, create the outbound parameters for message type EUPEXR with IDoc type IDCREF01. If you want to create IDocs from the proposal run, outbound parameters with the 'Test' flag are required in addition.

IDOC Types or BADI's

Hi,
Are there any standard IDOC types for the transactions
1. IW41 (Create PM Order Confirmation) - Inbound
2. Service order (IW31) - Outbound
Thanks
Sudheer

Hi Sudheer,
The IORD transaction requires the user status(as you correctly said)....However you can copy the report to a Z-Program and avoid this....
However, i am not sure about the impact of this....
Regarding the ALE paramters, this report expects the IDOC to be sent to a Logical system(partner type 'LS'). The report internally uses the FM IDOC_OUTPUT_IORDER01 to sent the IDOC. This sets the IDOC control record with Receiver partner as type 'LS' and the logical system name which is supplied.
If you want to sent to these a different partner type, some type of custom coding may need to be done...
Also pls post this question in the ABAP forum ....that is a more appropriate place....
Thanks,
Renjith

Create Idoc Type under ECC6

Hi folks,
I've created a new Idoc segment for an existing idoc (The original idoc doesn't have the fields I need). I'm now trying to create a new Idoc type taking into consideration the new Idoc Extension I've created. When I type my new idoc type and select 'basic type', I believe I should get prompted (somewhere) to enter the Basic Idoc type and Extension type, but when I create a new basic type, I don't get the option to add my new extension. And If I copy the original basic type, I don't get my new segments.
Can someone please tell me what I'm missing in the create new Idoc Process?
Cheers,
Steve

Hi Stephen..
According to ur Scenario (Adding new Segments to a Basic type ) , you should not create a Basic idoc type . Rather you should create an Extended idoc type in WE30.
That will ask for the Basic type and the new segments can be added here.
This is the Complete info:
1.
IDOC Enhancement
This is the Complete Steps and Info on this...with an Example...
Enhancing ALE
For example, if in an outbound interface you find that the IDOC type does not contain all the data you need to pass to the other system, you can extend the IDOC to accommodate the additional fields and enhance the ALE function modules to populate the fields. Similarly, if in an inbound interface, there is additional data that needs to be posted to the R/3 application, you can extend the IDOC type to have additional fields populated by the external system or translator or the other R/3 system and then enhance the inbound ALE function modules to post the additional data to the R/3 application.
let us use the SAP Customer Master application as an example. Specifically, letâs focus on the IDOC extension and ALE function module enhancement of IDOC type DEBMAS02 and message type DEBMAS (Customer Master) and the IDOC reduction of message type MATMAS.
IDOC EXTENSIONS
Letâs first look at the concept of IDOC extension. SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02, ORDERS02, and WMMBID01. By extending the Basic IDOC type, you are actually creating a new IDOC type. You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type.
Note that you should not add fields to existing segments but should create a new segment and associate it with an existing segment. This, in a nutshell, is the process of creating IDOC extensions.
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address (see Figure 1), DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
Determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save.
Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
2. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
From transaction WE30 or WEDI go to Development -> IDOC Types.
Enter ZDEBMASZ for Object Name.
Click on IDOC Type.
Click on Create.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter a description.
Enter.
You will see a display of the composite IDOC type with all segments, including Z1SADRX (see Figure 3).
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
3. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
Click on Display <-> Change.
Click on New Entries.
Enter DEBMAS for message type.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter your SAP R/3 release number for Release.
Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
4. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
From transaction WE30 or WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object name.
Click on Extension Type.
From the Development Object menu select Check.
Repeat the operation for IDOC type ZDEBMASZ.
A check log will be generated for each run with details of correctness or errors (see Figure 4).
In some situations it is possible to receive errors during the check process, especially segment length errors. The incorrect IDOC segment can be repaired and corrected by executing program RSEREPSG. This program checks the formal consistency and repairs incorrect segments. In test mode it will generate a log of formal correctness for the specified segment only. For the program to repair segments in normal mode, the underlying IDOC structures (DDIC structures) must be active. This program rectifies the lengths of the DDIC structures and not the fields themselves. RSEREPSG can also be used to change the person responsible for the object and the release flag.
Menu paths may vary slightly depending on the release/version of SAP R/3, but the procedures and the principles are the same.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
Reward if Helpful.

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

Urgent !!!!! Updating Inbound deliveries via Idoc type DELVRY05

Hi,
Is there a way to update an existing inbound delivery through the Idoc type DELVRY05. I'm able to create an Inbound delivery using this Idoc type. But im not able to update the same. There is a field VBELN, in segment E1EDL20. But whenever i pass the Inbound delivery in this field, it takes this field as a reference and creates a new Inbound delivery. And then the referenced Delivery is updated in the field LIFEX in table LIKP.
Thanks for your help. This is a little urgent.
Thanks
Albina

Hi Ganesh,
Sorry, I was referring to BAdI /SAPSLL/ECC_INBOUND, but got the name slightly wrong. As you say, the BAdI Method doesn't have a suitable parameter for making the updates - you would have to make the updates yourself in some asynchronous way (and I don't recommend it).
Yes, I understood your technical requirement, but you have not explained WHY you want to do it. I wonder which Customs Authority you are dealing with? I don't know of any that return additional document codes. Normally the inbound iDoc is used to convey error messages or status changes from the authority to the GTS Declaration. Here, it sounds like you are intending to use it for quite a different purpose.
Probably you should create your own Message Type, Process Code and Function Module to handle the updates. You could copy much of the code from the standard /SAPSLL/IDOC_INPUT_CCECUS, but it would be a substantial development.
Regards,
Dave

Transaction document for Idoc type

Hi Experts,
I am seeking little information about below Idoc type from POS to SAP IS Retail,
I would like to know that, what are the transaction documents generated in SAP IS Retail after executing of below inbound idoc type.
For example WPUUMS – It will create billing document for aggregate sales and material document for Goods movement.
Similarly, please help me for below Idoc type.
·         WPUBON
·         WPUTAB
·         WPUBWB
·         WPUFIB
·         WPUKSR

Hi Vanrajsinh,
I'd recommend you to go through the help.sap.com POS Inbound Interface for general information;
POS Interface - Inbound @ help.sap.com
and then crawl through related customizing in SPRO: Sales & Distribution > POS Interface > Inbound where you'll find the document types corresponding to individual IDoc types and IMG documentation per activity is also quite 'explicit'.
Not to leave you only with links, more information below but document types generated depend on the above config;
WPUBON - POS interface: Upload sales docs (receipts) non-aggregated;
Usually creates billing document and article document to post sales and goods issue per receipt, billing type and movement types can be defined in SPRO POS as above > Control Sales per receipt
WPUFIB - POS Interface: Upload Financial Accounting Interface SRS/POS
creates only FI posting (accounting documents) for pre-defined POS financial transactions; SPRO POS as above > Transaction Types for Financial Transactions and Trans.Type Cotrol of Fin.Trans.
WPUKSR - POS Upload Cashier Data
Cashier statistics, I've only used it for statistics (RIS, no transaction documents created)
WPUTAB - POS interface: Upload day-end closing POS / Payment List
Creates billing document to post payment per payment type if not already posted via receipts, SPRO POS as above > Payment List Control
WPUUMS - POS interface: Upload sales data (compressed)
as WPUBON but aggregated sales, SPRO POS as above > Aggregated Sales Control
WPUWBW - POS interface: Upload goods movements
Creates article documents to post goods movements
Note that you usually do not use all IDoc types at the same time as this would lead e.g. to posting a single receipt via multiple flows.
Hope this helps!
Regards,
Tomas

Creation of Service Contract from Inbound IDOC

Hi Experts,
I am using Inbound IDOC type ORDERS02 with message type ORDERS for creation of Sales Order. Now my requirement is like to create a Service Contract from that Inbound IDOC. The IDOC type contains all the data require to create a Service Contract. The scenario is like, after creation of Sales Order it will check for the corresponding Service Contract exits or not by querying on a Z table which contains all those entries.
So my idea is to create a Z Program, in which it will check for the Service Contract and will create the same by reprocessing the same IDOC or by calling some Function Module. Please suggest how shall i proceed to create a Service Contract.
Is there any way to reprocess the IDOC or to collect the Data from the IDOC segments pass them to a FM which is responsible for creation of Inbound IDOC. Please suggest if this is feasible.
Thanks in Advance.
Regards,
Priyabrata.

Actually there is problem with BDCDATA. Inside the FM it's calling transaction with help of BDCDATA. If i am creating a Sales order or contract alone its creating successfully. But when i am trying to create both, it's retuning sy-subrc '1001' after calling the transaction on the second attempt. Is there any problem with BDCDATA like we can't handle with less time gap? Please help and give your inputs.
Regards,
Priyabrata

Issue in using custom discount condition type in pricing agreement at Service Contract line item level

Hello
We are facing an issue while using a Z discount condition type in price agreement at service contract line item level.
A Z Condition type has been created in ECC and assigned to the pricing procedure. This pricing procedure is downloaded in CRM and determined in the service contract.
A condition maintenance group using this Z condition type is created in CRM and assigned to service contract item category.
Condition records are created in CRM for this condition type/condition maintenance group for specific products along with sales org and discount percentage.
But when the price agreement(using this condition type) is used at the item level of a service contract, the system throws errors (related to product/unit of measure and sales org, even though no issues seem to be there)and thus the price agreement is not allowed to be used.
If anyone has worked on such kind of scenario, please get in touch, I will share more details for the same.
Regards
Ankit Arora

Dear Ankit,
Once the pricing procedure is downloaded, please maintain the document pricing procedure at service contract header level, and maintain the customer pricing procedure at business partner sales area billing data.
In spro, maintain the pricing procedure for the combination of sales area, document pricing procedure, customer pricing procedure.
Please crosscheck whether the condition table is active or not.
Regards,
Maddy

How to map service contract data from ecc to crm

Hi Experts,
Please help me,how to map service contract data from ecc to crm system.
is there any perticular process.please let me know.
thanks in advance..

Hi Srinivasulu,
Create the service contract type of ECC and also item categories under it in ECC in CRM. Map the number ranges.
Check the Partners mapping from R/3 to CRM and that will be all.
I tried but in CRM in the transaction type internal number range is mandatory. So, if you create service contract in ECC with one number it will replicate to CRM but with different number. But you can see ECC number under the transaction history in CRM.
Good Luck.
Sharath.

Internal Order creation in ECC after creation of Service Contract in CRM

Hi,
I hv created Service Contract in CRM, but there is no internal order created referring this in ECC. Even no errors in CRM. What shall i chk for this.
rgds,
balu

Number range was changed in ECC for internal orders

Unable to create a service contract from IDoc BLAORD FM IDOC_INPUT_BLAORD

I've been testing creating service contracts using BLAORD and it appears that SAP does not have any way of creating a service contract using IDOC_INPUT_BLAORD. Inside this function a BDC is built and either ME31K or ME32K is called. There is processing that checks the service line package numbers, but it doesn't appear to be creating them (Maybe I'm overlooking something). When the BDC is being built the services screen is ignored. There is a user exit that could be used to populate the BDC for these screens.
I recently had to develop a custom BDC to create service contracts becuase, to the knowledge of our best ABAP-ers, there is no SAP standard functionality to create service contracts programmatically besides using a BDC. My custom BDC will fail when run in background because of a GUI control on the services screen. It runs fine in the foreground. The short dump is 'RAISE_EXCEPTION'. Short text: Exception condition "CNTL_ERROR" raised. Termination is occurring in CL_GUI_DOCKING_CONTAINER->CONSTRUCTOR. We're on ECC 6.0.
I checked the SAP Notes system and I was unable to find anything related specifically to contracts for this issues. I did see that SAP has released OSS notes for other BDC processes so that they would be able to run in background.
I am wondering if there is anyone who currently is able to create service contracts using IDOC_INPUT_BLAORD. My plan is to set up an RFC between SAP systems. The customer wants to be able to receive contracts on demand. Has anyone done this before for service contracts? What has your approach been? Is there anyway of having the function run in foreground when it receives a IDoc?
Thanks for your input,
Steve

Hello Steve,
Did you get a solution to Service Contract (Purchase) creation through BLAORD or through any other FM please?
BAPI_CONTRAT_CREATE does not handle services.
Have a similar requirement and trying to avoid BDC.
Thanks & Regards
Prashanth

IDOC type CRMXIF_ORDER_SAVE_M in CRM thru LSMW to create Service Contracts.

Similar Messages

Maybe you are looking for