KUNNR in IDOC COND_A

High,
I have some problems with sending conditions to the other systems. I have to send the condition which is relevant for only one customer. I have tabel with SO/DC/Customer (KUNNR) only. When I send the condition out via VK11 --> conrition info --> send condition, outgoing IDOC is created, but KUNNR field is not filled. KUNNR field is in IDOC documentation (WE60) and should be filled. What I have to do, to get customer number to the standard KUNNR field.
Thanks,
BR, Matija

Hi,
I checked in the customizing ant I have this in my table
Field name Data element Domain name
KUNAG KUNAG KUNNR
As I can understand you, there is something wrong with that?
BR, Matija

Similar Messages

How to create Idoc Cond_a

Hi
I have to generate outbound Idoc...for COND_A.
1) I created new pricing via VK11.
2) I executed report RSEOUT00.
3) Partner Profile for Cond_a i tried with both "Create Immidiately: and "Collects"
But i have found idoc is not geting genrated.
I want to use RSEOUT00 for sheduling purpose.Any thg i m missing above??
I can create the same idoc via VK12-Send Condition record also but it doesn't fullfill my requirement
Please help me out
Regards
Subham

Hi,
First you need to distrubute the idoc. if you dont want to use VK12 for sending.
You can write a custom program using FM MASTERIDOC_CREATE_COND_A to distrubute / create COND_A
Then you should use RSEOUT00 to send the idocs once its created.If you are using COLLECT IDOCS option.
Hope it helps.
Shanmugavel Chandrasekaran

IDOC COND_A Inbound Processing

We are trying to update Condition Price using COND_A (COND_A03)IDOC. Our functional requirements are similar to transaction VK11/VK12. We store the Contract Price and Contract Number coming from an external system in Condition Texts:Internel Comments and Permits. These correspond to two structure fields LV70T.LTX01 and LV70T-LTX01.
I did not know what field in IDOC these correspond to. If anyone worked on Condition Prices please let me know asap.
Regards
Mike

Hi Mike,
I am not sure if there is a field in COND_A03 Idoc to store your condition texts corresponding to your sturcture fields.
The function module to process the incoming COND_A03 Idoc is "IDOC_INPUT_COND_A". You can view this function module using Tr.Code SE37 in R/3.
I would suggest debugging( in foreground )this function module using Tr. Code WE19 with a sample COND_A03 Idoc. Try to see if you can find any corresponding fields in the IDOC for your fields LV70T-LTX01 AND LV70T-LTX02.
If you can't find these fields in IDoc, this functional module also has a CUSTOMER-FUNCTION, where you should be able to write a custom user exit to populate the fields with custom or enhanced IDoc.
Hope this helps.
Regards,
Sam Raju

Problem when creading IDOC COND_A

Hello all,
I am facing a problem in recognizing changes in conditions,
when changing a condition threw VK12, and choosing "create with reference" , the system creates a new record from the date you choose and closes the previous conditions to the day before.
If the date you choose is in the pat (or today) then when you want to create IDOC's of the last changes you will see only one segment in the IDOC - the new one (ther wont be an update of the old one), if the date is in the future then there are 2 segments in the IDOC.
Does any one know how to solve this problem?
Thanks,
Naama

Hi,
Do you refer to IDOC WP_PLU02?
Check in tcode BD52 for message COND_A the tables and fields.
Perhaps Best Practice 'R33: Store connectivity' will help you (see in http://help.sap.com/bp_bblibrary/600/html/R33_EN_DE.htm)
I hope this helps you
Regards,
Eduardo

IDOC COND_A - INBOUND

Hello ALL.
I'm using IDOC COND (FM: IDOC_INPUT_COND_A), it works perfectky when creating a condition record.
Now I want to modify it, does the IDOC works for that process as well ? . . .
If it works, wich fields i need to fill in in order to work in that way . . .
Thanks in advance .
Kind regards.

Hi Mike,
I am not sure if there is a field in COND_A03 Idoc to store your condition texts corresponding to your sturcture fields.
The function module to process the incoming COND_A03 Idoc is "IDOC_INPUT_COND_A". You can view this function module using Tr.Code SE37 in R/3.
I would suggest debugging( in foreground )this function module using Tr. Code WE19 with a sample COND_A03 Idoc. Try to see if you can find any corresponding fields in the IDOC for your fields LV70T-LTX01 AND LV70T-LTX02.
If you can't find these fields in IDoc, this functional module also has a CUSTOMER-FUNCTION, where you should be able to write a custom user exit to populate the fields with custom or enhanced IDoc.
Hope this helps.
Regards,
Sam Raju

Mapping pricing conditions cond_a

I am working on sending pricing condition records from SAP to XI - idoc (cond_a) to flat file scenario.
In the mapping, on the source side, there is segment - E1KOMG (Occurence - 0..1) that is mapped to - UpdateInsertKOMG (Occurence - 0..Unbounded) on the right (target).
Right now we get one KOMG record in the flat file. We need two KOMG records in the flat file.
I was told to modify the UpdateInsertKOMG on the right (target) to accomplish this.
How to accomplish this?
Thanks.

1-change the ocurrance of the segment to 0.N
If I want to use this approach, how do I change the occurance from 0 to N.
the abap team has to do this
In the source I will always have one segment of KOMG and mulitple KONP.
you need all the values of KONP in the file?
for exmaple this is your structure:
<IDOC>
<E1KOMG>0.1
<KONP>0.n
<KONP>123
<KONP>aasd
<KONP>gtr
</E1KOMG
</IDOC>
the file should be
XXXX,XXX,123,aasd,gtr
something like that? actually you have the structure of the IDoc as my example and you only get one value into the file??
if that is true, you need to modify your mapping like:
KONP-->targetsegment --> doing this you will create at target side many segments as KONP values you receive
KONP>splitByValue(eachValue)->targetfield -->many field in the target segments as KONP values.

WE-19 Inbound Idoc Process - Status Code 51

Hi,
I generated Outbound idoc COND_A successfully to send it out to XI. I used same Idoc again in WE19 and changed partner details and tried Inbound Processing. Its giving me error code 51 ("ISO Currency USD can not be converted unambiguously to SAP currency for E1KOMG" )
Any Idea how to fix this error. basically I did not changed anything.
Message was edited by: Ram Krish

Appana,
Thank you very much for your reply.
I did setup all parameters as Iam getting this Idoc as an Inbound to R3 as well. Thsi Idoc will be both Outbound and Inbound to R3.
I successfully sent this Idoc to XI. and then as I wanted to test the same Idoc for inbound, I changed Paramters according to my setup.
Sequence of status are
74 - created with test transaction
50 - Idoc added
64 - Idoc ready to be transferred to Application
62 - Idoc Passed to Application
51 - ISO currency USD can not be converted unambiguously to SAP currency for KOMG
I looked at several fields in E1KOMG segment and changed one of the currency field to USD which didn't help to fix this error.
I really appreciate any help to fix this error.

Export Material and Price Data with IDOC or BAPI?

Hi SAP Experts,
I found two ways to implement a Master Material and Price Export to an external system, first with IDOC MATMAS01 and Idoc COND_A with an enhancement VKOE0001 PRICING CONDITION.
Here I don't know how I can match a material with tht sales price?
And the second one with the BAPI. But how I create a BAPI for Material and Sales Price?
And which is the better way?
Thanks and Bye,
Frederic

Amit,
it seems that the FU BAPI_MATERIAL_SAVEDATA is only for Create and Change Material Master Data. Is that correct?
I've following Use Case, I will send e.g. one Material with the sales price to an external system (later all material with their sales price). And for that case I'm searching for a solution. Can you bring me on the correct way to implement something like that.
I would be very pleased if you can help me.
Bye,
Frederic

Regardig the extension of the Idoc

Hi Experts,
                We are using an Inbound Idoc.
              I extended the idoc COND_A, becoz we are having some custom fields in the IDOC.
         For this we have an Exit in the FM IDOC_INPUT_COND_A.
But the data coming to inbound would be of various tables which contains the custom fields.
      How do i update the data in the database tables.
For EX table A contains 4 custom fields that are to be updated,table b contains 2
custom fields that are to be updated.
       How do i do this??
Thanks and Regards
Rajesh.

Hii..
SAP provides the Function module exits to process the Extended idoc type.
Check this info...
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.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
reward if Helpful

Problem with Purchase info rec's(RM06IBI0)

Hi experts,
I have a querry, we are uploading PIR data through the program RM06IBI0, here if we enter any header condition type(KNTYP = H) (Like PB00) as the first record no problem is there.But, If we are not sending this Header condition type then, We are getting an error.
Is there any rule while updating PIR data throgh the program RM06IBI0, we have to enter first PB00 ?
Can any body explain this briefly.
Thanks in advance.
Regards,
Sandya.

Hi,
You are right. You need to give PB00 - Base price as the first condition. If you hace a different condition type in your datafile for upload check with your MM consultant who can help you in customizing.
And another point with respect to conditions in prg: RM06IBI0 is that if you have multiple conditions with scales ( value / quantity ), this would not work & in this case you need to load conditions separately by IDOC: COND_A / COND_A02
Hope this helps.
Best Regards, Murugesh

Material and Price export to an External System

I've a Problem, I will send Materials with sales Price from SAP to an external System. I will use the IDOC MATMAS01, but I can't send the price with it? Is that correct? How I can send the sales Price for each Material? Is it possible to send more than one Material (mass export) with MATMAS01 per process? Or I had to define a Product or Price Catalog?
Or is there a better way by using a BAPI for this use case? Which BAPI?
Thanks

Thanks for the answers, now I've two ways to implement that, first with IDOC MATMAS01 and Idoc COND_A with an enhancement VKOE0001 PRICING CONDITION. And the second one with the BAPI.
Which is the better way?
And how I create a BAPI for Material and Sales Price?
Thanks

Condition type requirement

Hi Team,
I have a condition type requirement where C.Type ZXYZ has to be determined only when ZABC (List price) condition record is determined from a specific key combination only.
Would like your valuable inputs for achieving this.
Thanks in advance.
Best rgds
Rama

Thanks JM for the approach suggested. I will configure as stated and check.
Thanks JP for getting reply to one of my questions .
Few things to discuss,
My actual access sequence for ZABC condition type looks as shown below. First 2 levels are customer specific. Last 2 levels are Material specific.
1. ZABC condition records are created by an idoc (COND_A) in my case. Will i be able to upload condition supplement value here.
2. Can i create condition supplement records in mass load ? System already has huge amount of customer specific prices.
3. Do i don't require any access sequence now for ZXYZ condition type ?

Export Material and Price Data

Hi SAP Experts,
I found two ways to implement a Master Material and Price Export to an external system, first with IDOC MATMAS01 and Idoc COND_A with an enhancement VKOE0001 PRICING CONDITION.
Here I don't know how I can match a material with tht sales price?
And the second one with the BAPI. But how I create a BAPI for Material and Sales Price?
And which is the better way?
Thanks and Bye,

Hi Frederic,
I think you have posted the question in the wrong Forum. I think, you should post it in ABAP forum to get the answer.
Thanks and Regards
Nitin jain

DEBMAS06 - posting for internal number

Hi,
I am able to post DEBMAS06 idoc in R3 and create customers with external number.
How to create customer with internal number range ? i tried sending in blank value for KUNNR field, idoc failed to post.
Any ideas?

Hi,
I think you can try to use fm BAPI_CUSTOMER_GETINTNUMBER .
D Bye...

Error while trying to post inbound idoc of message type COND_A

Hi,
I am getting error while trying to post inbound idoc of message type COND_A.
If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
and if providing value in above fields then dump is coming.
How to solve ?
Plz do reply
Thanks
Mohit

I do not see any reason why you would need to use COND_A04 if COND_A01 is working.
What if you could get COND_A04 to post and you would face the same result as in COND_A01?
If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
fixed a situation where the vendor number was not validated.

KUNNR in IDOC COND_A

Similar Messages

Maybe you are looking for