Home › Master Data › Maintenance of Output Condition Records for Purchase Orders

Maintenance of Output Condition Records for Purchase Orders

Posted on October 23, 2014 by giscodeguru — 2 Comments

A brief on output Condition Records

Output messages are basically used by the SAP System to remember the preferred mode of communication with the Vendors. Some Vendors may accept Purchase Orders though Fax and others through EDI etc. The output condition records are used to record these output preferences for each Vendor. The Output Message Determination works by the Condition technique which is used in many other areas in SAP such as pricing. The Output Condition records are maintained in the Table NACH.

Below is a snapshot of 2 sample records from the NACH table. When the system finds the

Cl. CondRecNo. Created by Created on U Tab App CTyp VarKey Valid From to SrchTerm Funct Partner Med No. Time
010 0000000021 123456 8/31/1999 B 505 EF Z001 Y0030004 EK 1 0 4
010 0000000022 123456 8/31/1999 B 508 EF Z001 Y0030004156001 EK 1 0 4

CONDITION TECHNIQUE

TNAPR

The following requirements can be satisfied through

  1. Send the Purchase Orders via Fax to all Vendors in Purchasing Organization XXX.
  2. Send the Purchase Orders via Fax to all Vendors in Organization YYY, except a few for whom use EDI as the transfer medium.

Fields worth remembering

  1. NACHA  Medium
  2. KSCHL Ouptut Type
  3. VAKEY Variable Key
  4. KAPPL Application (Purchase Orders/PRs/
  5. SPRAS Language
  6. Dispatch Time

NACHA

Analysis on the Production System

Find the Output types used in the Production system in the past one year by downloading records from the NAST table. Looks for all the records in NAST relevant to the Purchase Organization or Plant. This can be done in two steps

  1. Find all the POs in adate range from table EKKO (SE16, EKKO, Export to Excel)
  2. Copy the PO numbers from Step 1 and paste in OBJKY field of NAST table to get all the records for these POs.

BUSINESS SCENARIO

Consider a case where a business is implementing a different Purchase Order Doc Type ZA. This Purcahse Order has a different Number Range, specifies what item categories can be procured through ZA, different display fields etc. Previously the SAP system had output condition records maintained for Doc Type NB. Now, as part of new implementation, the business decided to duplicate the existing condition records to the new document

MASS UPLOAD USING LSMW

record the screens

Create a structure with field names

Background processing  is faster

View error – If a failure is due to duplicate record, it is not really a big deal

TESTING

Tagged with: , ,
Posted in Master Data, Purchasing
2 comments on “Maintenance of Output Condition Records for Purchase Orders”
  1. Yash says:
    October 27, 2014 at 7:26 am

    Thank you very much

    Reply
  2. giscodeguru says:
    June 5, 2015 at 2:32 am

    Yash, thanks. I’m glad you found this useful.

    Reply

Leave a comment