add a new field to field catalog in billing output

[Former Member]

Hi Experts

can anyone tell me whether I can add 'item category' to field catalog for application V3. and how can I do this? I want to create an access sequence-bill to party/item category, is that possible?

thanks a lot!

elly

[Former Member · Accepted solution]

Hi Xiao,

In standard SAP communication structure KOMKBV3 works for output processing of a billing document. This structure does not contains a field for item category as such. This means that even if you assign a field in the field catalog, it won't work as the field has to be available in this structure.

You really need a good abaper to help you in carrying these steps. The steps are as below:

1) The new field for item category is first required to be entered into include KOMKBZ5.

2) If you also want to use a new field for the setup of condition tables (key field) it must also be included in the structure KOMBZ (contained in KOMB).

3) Once this field is added to the structure, you add this new field to the field catalog.

4) create your condition tables using this new field.

5) Since this field is added by you, Standard SAP is not going to flow the value for item category into this field during billing output processing. You have to flow the item category value into this field. To flow that value from the billing document into this communication structure, please insert your code in USEREXIT_KOMKBV3_FILL (header fields in billing document) to move the value from billing document into the communication structure

if you want to add this new field at billing document item level(may be for use with invoice lists item printouts), you can follow the same process but the communication structure include and user exit will change

for item level - include to append is KOMKBZ5 (in KOMPBV3) and the user exit is USEREXIT_KOMPBV3_FILL (item fields in billing document)

Though you can achieve your solution using the above logic, i am still curious to know the scenario which is making you add the item category into a communication structure for output determination. It does not sound right. Will be gr8 if you can share the scenario with me.

thanks

Kapil Sharma

[Former Member · Accepted solution]

Hi Kapil

thanks for your detail explanation, the business scenario is :users want to have RD01(copy of RD00) automatically printed to their printer. I have created an access sequence-sales org/bill to to cover this,but we have another business scenario,invoice for debit memo request, it can be the normal business, meaning for MFG, but also be non-trading goods, the only difference for these two types are the item category and account assignment group, later user don't want to be printed automatically, both are in item level, do you have a good suggestion?

thanks in advance.

elly

[Former Member · Accepted solution]

Hi elle,

Unfortunately, in standard SAP, outputs for a billing document are driven by partner, sales area, destination region, foreign trade indicator and so on. All these settings are available at the header level of a billing document. If you cannot use any of these fields for determining your output, you need to add your own fields.

In the given situation that you only have item category and AAG to differentiate between the two processes (MFG & Trading), your only option is to add the new field to communication structure.

My apprehension to not to use Item category or any other item level field was because of the reason that a billing document can have multiple item categories and if you use item category to decide your billing output, your code will stuck when SAP encounters more than 1 item category in the document. For such scenarios, i would suggest you to make an assumption with your client that the item category or AAG from the first line item will decide the print output and you make the selection in the code using statement "select single from". This statement will pick up whatever is the first item category from the billing document. Meanwhile, if you can try some other alternatives, may be seperating the billing document types for the two processes.

Thanks

Kapil Sharma

[Former Member · Accepted solution]

Hi Kapil

You have answered all my queries and provide the proposals.

thanks a lot!

have a

nice day

elly.

[Former Member · Accepted solution]

Hi Elly,

You are welcome.

Thanks

kapil sharma

[Manoj_Mahajan78]

Hi..

Below is process of adding filed to catalogue in Pricing..

Follow below procedure as its same as condition technique...

Add a field to a new condition table in Pricing (Condition Technique):-

I will explain you the process with below example...Please follow steps in below sequence-

Try to add the filed from the field catalog. In case the required combination field is not there, you can add the field through the following process to filed catalog and create the condition table. It is most common that one or other time we need to use this function while configuring multi tasking & complex Pricing Architecture.

Here I'm giving a simple guide to add fields to the Pricing Field Catalogues:

For example you want to use field PSTYV ('Sales document item category') that is included in structure KOMP ('Pricing Communication Item') as a key for a condition table.

When you create a condition table (Transaction V/03), however, the system does not propose the field in the field catalog.

Condition access, field catalog, allowed fields, KOMG, KOMK, KOMP, KOMPAZ, KOMKAZ, PSTYV are the other terms which we need to know about, to add Fields.

Reason and Prerequisites:

For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG ('Allowed Fields for Condition Structures').

Proceed as follows:

1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV as a domain.As a short text, you can use, for example, 'ZZ - sales document item category' and as a field label, you can use the field labels of PSTYV.Save, check and activate your entries.

2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make the following entry:

Component Component type:

ZZPSTYV ZZPSTYV

Save, check and activate the change you made.

3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures KOMG and KOMP because structure KOMPAZ is included in both structures.

4. Call up Transaction SPRO. Navigate to 'Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control' and execute 'Define Condition Tables'.

Choose 'Conditions: Allowed fields' and include ZZPSTYV as a new entry.

5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.

6. Supply the new field you defined by including the following source code line in USEREXIT_PRICING_PREPARE_TKOMP:

MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.

In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ.

Consider that you can also use this note as a help if you want to use other customer-specific fields as key fields in a condition table.

For header fields, use structure KOMKAZ instead of structure KOMPAZ and

USEREXIT_PRICING_PREPARE_TKOMK instead of

USEREXIT_PRICING_PREPARE_TKOMP.

For more information, see Transaction SPRO via the path 'Sales and Distribution -> System Modifications -> Create New Fields (Using Condition Technique) -> New Fields for Pricing' and OSS Note 21040.

REWATD IF U FINDS THIS AS HELPFUL..

Regds

MM

[shaik_a]

Hi Manoj,

I understand this was posted long time ago, but I wanted to let you know it is still helping people like me. I wanted to say Thanks for sharing your knowledge.

Thanks,

SMA.

Edited by: S M A on Jan 13, 2012 6:21 PM

[Former Member]

hi,

Yes u can add the item category-PSTYN in field catalog

<b>menu path:</b>

spro->img>sd->basic function->output control->o/p determination>maintain o/p determination for billing documents>maintain condition table->here click field catalog:Messages for billing documents-> here click new enteries ikon---> feed the item category firld name

hope this help u

regards,

Arun prasad