Unused fields in PO items tabs - EKPO

[Former Member]

Hi all,

We are planning to use following fields from table EKPO (PO ITEM) for passing some information as I found these fields are not used currently..

A) Date field

1) DRDAT - Last transmission

2) NLABD - Next forecasting delivbery schedule transmission

3) NFABD - Next JIT delivry schedule

B) Character field (20)

1) GRANT_NBR - Grant

My problem is that I am not able to see the above fields in Purchase orders, even though they are in table EKPO.

Can some one guide me in this matter.

Thanks,

Vengal Rao.

[Former Member · Accepted solution]

 A) Date field   
 1)   DRDAT  - Last transmission
 2)   NLABD  - Next forecasting delivbery schedule transmission
 3)   NFABD  - Next JIT delivry schedule
.

All the above fields are relevant for Scheduling Agreement release order and are not relevant for standard Purchase Order.

NLABD -> Forecast (FRC) delivery schedule

NFABD -> Just-in-Time (JIT) delivery schedule

and of course DRDAT have details of last transmission of the above.

Read this document: [SA Releases (Forecast or JIT Delivery Schedules)|http://help.sap.com/saphelp_dimp50/helpdata/en/75/ee0fb555c811d189900000e8322d00/content.htm]

Read about field GRANT_NBR [Public Sector Management |http://help.sap.com/saphelp_erp60_sp/helpdata/en/81/492a3beb116d61e10000000a11402f/content.htm]

Hope this helps!

Reetesh

Edited by: Reetesh on Dec 15, 2011 8:51 PM

[Former Member · Accepted solution]

Hi Reetesh,

Thanks for the reply,

Can you help me to locate TWO date fields and ONE character field having around 15 to 20 chracters in the standard PO item level area which I can use for passing information related to a courier ie FEDEX.

Regards,

Vengal Rao.

[JL23 · Accepted solution]

append table EKPO with Z-fields and use a user exit to show and maintain those fields in an extra tab of your PO.

[Former Member · Accepted solution]

NP!

As Jürgen said you need to append the table (as there are no standard field as per your requirement) and then you also need a screen-exit to, to and fro data entered on the screen to the table and vice-versa.

Look at exit MM06E005 or check out yourself exits available User Exits in Transaction ME21N

Hope you find these useful.

Reetesh