Edit Field Catalog fo Output purchase Order

[Former Member]

Does anyone know which is the transaction code to add new fields to the purchase order access sequence tables for output types ?

For example, in sales you can create tables (access sequence ) to determine the output type, how can I edit the field catalog that feeds this tables in purchasing output type.

Kind Regards

[Former Member · Accepted solution]

Hi,

It is under IMG ---> Material Management ---> Purchasing ---> Messages ..... where you can define the condition table setting.

Cheers,

HT

[Former Member · Accepted solution]

Hello,

I did try to look here, but the only thing I found was the way to create new tables but no to add new fields.

Kind Regards

[Former Member · Accepted solution]

Hello,

T-CODE M/59 is the table creation, which is the T-CODE to add new fields to the catalog.

Kind Regards

[Former Member · Accepted solution]

Hi,

When clicking on 'Define condition table for POs', SAP will populate the new small window which provide three options -

1) Create condition table;

2) Change condition table; and

3) Display condition table.

If your field catalog has already been part of the current SAP table, then you can select 'Change condition table' where you can enter your related condition table number and move the related field catalog from the right to the left. If this field was not defined as part of the condition table (i.e. you do not see it in the list of field catalogs in the right hand side of the condition table), then you will have to activate the related user exit to append a new field catalog before updating your current table via configuration.

Cheers,

HT

[Former Member · Accepted solution]

Hello,

I have to use a user exit to add a new field in the catalog ? how should I do that.

Kind Regards

[Former Member · Accepted solution]

David,

I can't answer your question directly but I can propose an alternative:

If you are looking for another field to trigger output determination, you may want to consider having an ABAP developer create a custom requirement for that output type. Requirements can make simple validation checks and if it passes (sysubrc = 0) then the output is proposed, if not, then output is not proposed.

Create requirement @ Materials Management > Purchasing > Messages > Output Control > Maintain Requirements for Message Control

Assign requirement to output type @ Materials Management > Purchasing > Messages > Output Control > Message Determination Schemas > Define Message Schema for Purchase Order.

I hope this helps

[Former Member]

Check OSS Note 39462 on steps to add additional fields to the field catalog for Purchase order messages condition tables.

The communication structure to be maintained can be taken from table T681Z. Table T681Z can be displayed with Transaction SE16.Use 'B' for message determination and application EF for purchase order.

Thus the structure for purchase orders to be maintained is KOMKBEA.

The following section describes how to include field 'User ID' in the structure.If other applications or fields are used, the following example can be used in a modified form.

Solution

1. You must include field ZZUSNAM in communication structure KOMKBEA.In this structure there is an include that is provided for additional fields.In this Include KOMKBZ you must include the field with the name ZZUSNAM. ERNAM can be used as the domain in this case.

2. The same field must also be included in structure KOMB in Include KOMBZ (the same procedure as under point 1).

3. In table T681F use Transaction SM31 with key B, EF to add the same field. You can do this by overwriting an existing field.

As of Release 4. 0 you can use view V_T681F in Transaction SM30 for that purpose. Enter usage 'B', your application and field group '001'.

4. In the message determination, the system runs perform USEREXIT_KOMKBEA_FILL. This perform is in program RVCOMFZZ.

The source code should be changed as follows:

FORM_USEREXIT_KOMKBEA_FILL.

COM_KBEA-ZZUSNAM = SY-UNAME.

ENDFORM.

Use the current user for SY-UNAME.Any EKKO field with the following syntax can be used.COM_KBEA-ZZFIELD1 = COM_EKKO-field.

5. After making this change, you must create a new condition table and an access sequence that contains the new field.If a new access sequence and condition table have already been created before changing the communication structure, this must now be deleted again.Points 1 to 5 must be carried out in sequence.

6. Note that the syntax check in Include RVCOMFZZ can deliver errors.Check the entire function group (according to Note 2152).

[former_member660933]

Hello,

M/59 for creating new condition record for PO output type.

path >> SPRO >> MM >> Purchasing >> messages >> access sequence >> define access sequence for PO

path >> SPRO >> MM >> Purchasing >> messages >> condition tables >> define condtion table for PO

Regards,

Shailesh