Table invoices without output messages

Hi,

check this out

Message control

Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.

In outbound programs(function module) that use message control the key of the

application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the

message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.

The parameteers passed to the function module are

IMPORTING PARAMETERS

OBJECT LIKE NAST

It contains documents key.

CONTROL_RECORD_IN LIKE EDIDC

It contains the partailly filled control record

EXPORETING PARAMETER

OBJECT_TYPE

CONTROL_RECORD_OUT LIKE EDIDC

TABLES

INT_EDID LIKE EDIDD

The internal table used to fill the data records in the same order as they exists in

the IDOC.

The important parameters that should be filled in the custom function module are

CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.

===========================================

Message control and output type. In R/3, message control is a mechanism by which documents are output based on certain selection criteria, requirements, and sequences. Message control determines the type of document, its timing, number, and medium (print, fax, ALE, or EDI.). Outbound messages in SD (Sales and Distribution) and MM (Materials Management, Purchasing) are created and processed by message control records. The output records are stored in the NAST table.

Message control uses the condition technique. The conditions for creating an output message are stored in condition tables that have selection fields picked from a catalog of application fields/tables. To determine if an application document qualifies for output, search strategies are used through access sequences, output procedures, and requirements. Once a message qualifies for output, message control modules use the parameters set in the condition type or output type to determine the timing of transmission and the medium of the message. The output type also specifies the program or module to be invoked to create the output.

Message/output determinations are concepts applicable not only to EDI and ALE, but also to other output mediums.

also check this link...

http://www.erpgenie.com/sapedi/messagecontrol.htm

Feel free to revert back.

--Ragu

Hi

If there isn't any hit for a certain invoice in NAST table it means that invoice hasn't a message.

So you should create a query for the NAST table where KSCHL is RD00.

TABLES: VBRK.

SELECT-OPTIONS: SO_VBELN FOR VBRK-VBELN,

SO_FKDAT FOR VBRK-FKDAT.

DATA: T_NAST LIKE STANDARD TABLE OF NAST WITH HEDAER LINE.

DATA: BEGIN OF T_VBRK OCCURS 0,

VBELN LIKE VBRK-VBELN,

END OF T_VBRK.

START-OF-SELECTION.

SELECT VBELN FROM VBRK INTO TABLE T_VBRK

WHERE VBELN IN SO_VBELN

AND FKDAT IN SO_FKDAT.

IF SY-SUBRC = O.

SELECT * FROM NAST INTO TABLE T_NAST

FOR ALL ENTRIES IN T_VBRK WHERE KAPPL = 'V3'

AND OBJKY = T_VBRK-VBELN

AND KSCHL = 'RD00'.

ENDIF.

Max