topic Re: IDOC checklists in Application Development and Automation Discussions

IDOC checklists

Former Member — Tue, 06 Jun 2006 05:59:56 GMT

Hi all,

Please let me know the various IDOC review checklists to be maintained for programming IDOC.

Regards,

B.Anandha Krishnan

Former Member — Tue, 06 Jun 2006 06:14:41 GMT

1) Interface Specific

A) CHECKLIST SPECIFIC TO INBOUND / OUTBOUND INTERFACE

Sl no. Program check Self Review (Y / N) Independence Review

(Y / N) Remarks

(defect id in case of defect or remark where applicable)

1. New Function Group created for every interface.

2. Data sets are written with proper length specification avoiding hard coding of length.

3. For files names

• Table is used to read the relevant file name

• After reading from the table, translate to lower case is done, if the table stores file names only in uppercase.

• If no entry found in the table, global constant used for taking file name

4. • Proper error handling and notification is done.

• Adequate Error/Warning/Information messages are provided.

5. • Inbound interfaces should check for blank records in the input file before taking it up for processing.

• Outbound interfaces should not have any blank lines in the output file.

6. Variant is defined and included in the request number.

<b><b>PLZ MAKE REWARDS IF HELPFUL..</b></b>

dani_mn — Tue, 06 Jun 2006 06:45:20 GMT

1. Create IDOC segments.

2. Create IDOC types.

3. Create Message types.

4. assign message type to idoc type.

use this FM to get determine ale model "ALE_MODEL_DETERMINE_IF_TO_SEND"

Fm to create and send idocs for outbound process. "MASTER_IDOC_DISTRIBUTE"

Maintian inbound process code using we42 and assign a FM to it for processing your logic.

Regards,

Wasim Ahmed