Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Change the records in NAST table

Former Member
0 Kudos

Hi,

In sales order TCODE VA01, the output is creating if we change the or add new items. There are some extra records for that SO in NAST table with the value 'X' in field ACTIV & 0 in processing status. How to delete or change the values in this table.

Thanks,

Sadiq

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi shaik,

NAST is used for message status.

it is a system table.

it contains 82 fields.

Change message records (table NAST) and additional message data (this data can only be determined via the message determination

see this link

http://abap.wikiprog.com/wiki/BAPI_PO_CHANGE.

You can use the R/3 message concept to trigger IDocs the same way as you trigger SAPscript printing.

One of the key tables in R/3 is the table NAST. This table records reminders written

by applications. Those reminders are called messages.

Every time when an applications sees the necessity to pass information to a third

party. a message is written to NAST. A message handler will eventually check the

entries in the table and cause an appropriate action.

The concept of NAST messages has originally been designed for triggering

SAPscript printing. The very same mechanism is used for IDocs, where the IDoc

processor replaces the print task, as an IDoc is only the paperless form of a printed

document.

The messages are usually be created using the condition technique, a mechanism

available to all major R/3 applications.

The conditions are set up the same way for any output media. So you may define a

condition for printing a document and then just change the output media from

printer to IDoc/EDI or ALE.

Creating NAST messages is a standard functionality in most of the SAP core

applications. Those applications - e.g. VA01, ME21 - perform calls to the central

function module MESSAGING of group V61B. The function module uses

customizing entries, mainly those of the tables T681* to T685*.

A NAST output message is stored as a single record in the table NAST. The record

stores all information that is necessary to create an IDoc. This includes mainly an

object key to identify the processed object and application to the message handler

and the sender and receiver information.

Creating NAST messages is a standard functionality in most of the SAP core

applications. Those applications - e.g. VA01, ME21 - perform calls to the central

function module MESSAGING of group V61B. The function module uses

customizing entries, mainly those of the tables T681* to T685*.

A NAST output message is stored as a single record in the table NAST. The record

stores all information that is necessary to create an IDoc. This includes mainly an

object key to identify the processed object and application to the message handler

and the sender and receiver information.

thanks

nagendra

2 REPLIES 2

former_member181995
Active Contributor
0 Kudos

may be i would not suggest to delete the entries from NAST.

but you can write small piece of code in se38 to delete these entries since it is very nedded.

Former Member
0 Kudos

Hi shaik,

NAST is used for message status.

it is a system table.

it contains 82 fields.

Change message records (table NAST) and additional message data (this data can only be determined via the message determination

see this link

http://abap.wikiprog.com/wiki/BAPI_PO_CHANGE.

You can use the R/3 message concept to trigger IDocs the same way as you trigger SAPscript printing.

One of the key tables in R/3 is the table NAST. This table records reminders written

by applications. Those reminders are called messages.

Every time when an applications sees the necessity to pass information to a third

party. a message is written to NAST. A message handler will eventually check the

entries in the table and cause an appropriate action.

The concept of NAST messages has originally been designed for triggering

SAPscript printing. The very same mechanism is used for IDocs, where the IDoc

processor replaces the print task, as an IDoc is only the paperless form of a printed

document.

The messages are usually be created using the condition technique, a mechanism

available to all major R/3 applications.

The conditions are set up the same way for any output media. So you may define a

condition for printing a document and then just change the output media from

printer to IDoc/EDI or ALE.

Creating NAST messages is a standard functionality in most of the SAP core

applications. Those applications - e.g. VA01, ME21 - perform calls to the central

function module MESSAGING of group V61B. The function module uses

customizing entries, mainly those of the tables T681* to T685*.

A NAST output message is stored as a single record in the table NAST. The record

stores all information that is necessary to create an IDoc. This includes mainly an

object key to identify the processed object and application to the message handler

and the sender and receiver information.

Creating NAST messages is a standard functionality in most of the SAP core

applications. Those applications - e.g. VA01, ME21 - perform calls to the central

function module MESSAGING of group V61B. The function module uses

customizing entries, mainly those of the tables T681* to T685*.

A NAST output message is stored as a single record in the table NAST. The record

stores all information that is necessary to create an IDoc. This includes mainly an

object key to identify the processed object and application to the message handler

and the sender and receiver information.

thanks

nagendra