A02 bb config_guide_en_jp

EHP4 for SAP ERP 6.0

March 2011

English

Communication Automotive (A02)

SAP AGDietmar-Hopp-Allee 1669190 Walldorf

Building Block Configuration Guide

Germany

SAP Best Practices Communication Automotive (A02): Configuration Guide

Copyright

© Copyright 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG Page 3 of 169


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include Field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Contents

Communication Automotive............................................................................................................5

1 Purpose................................................................................................................................... 5

2 Preparation.............................................................................................................................. 5

2.1 Prerequisites..................................................................................................................5

3 Configuration........................................................................................................................... 5

3.1 Configuration in the Supplier System............................................................................5

3.1.1 Output Determination................................................................................................5

3.1.2 Partner Profile, Only Basic Data..............................................................................28

3.1.3 Partner Profile Inbox................................................................................................31

3.1.4 Inbound Function Module........................................................................................34

3.1.5 Creating Message Output for Outline Agreement....................................................35

3.1.6 Maintaining tRFC Port.............................................................................................36

3.1.7 Maintaining a File Port.............................................................................................37

3.1.8 Activating IDoc Inbound...........................................................................................40

3.1.9 EDI Invoice Parameters...........................................................................................41

3.1.10 Creating Message: Sales and Distribution YANO...................................................41

3.1.11 Number Range........................................................................................................42

3.2 Configuration in the OEM System...............................................................................42

3.2.1 Output Determination..............................................................................................43

3.2.2 Activating Requirement 111 for Output Control.......................................................50

3.2.3 Partner Profile, Only Basic Data..............................................................................50

3.2.4 Partner Profile Inbox................................................................................................53

3.2.5 Maintaining a tRFC Port..........................................................................................55

3.2.6 EDI Invoice Parameters...........................................................................................56



Communication Automotive

1 PurposeThe purpose of this document is to describe the general configuration steps required to manually set up the configuration within the system landscape that has already been installed using the corresponding installation or configuration guides.

If you do not want to configure manually and prefer an automated installation process using eCATTs and BC Sets, use the SAP Best Practices Installation Assistant.

2 Preparation

2.1 PrerequisitesBefore you start installing this building block, you must install prerequisite building blocks. For more information, see the building block prerequisite matrix (Prerequisites_Matrix_[xx]_EN_JP.xls; the placeholder [xx] depends on the SAP Best Practices version you use, for example, Auto refers to the SAP Best Practices for Automotive Package: Prerequisites_Matrix_Auto_EN_JP.xls). This document can be found on the SAP Best Practices documentation DVD in the folder \Auto_JP\Documentation\.

3 Configuration

3.1 Configuration in the Supplier System

3.1.1 Output Determination

UseIn this step, configurations regarding Message Output determination for Scheduling Agreement, logistic invoice verification, outbound delivery, billing document and shipment are installed.

3.1.1.1 Maintaining Output Determination for Scheduling Agreement Release

3.1.1.1.1 Changing Data Catalog for Condition

UseAdd Supplying Vendor to field catalog.

Procedure

1. Access the activity using one of the following navigation options:

Transaction code SM30



2. On the Maintain Table Views: Initial Screen, enter the following data:

Table V_T681F



3. Choose Maintain and confirm the message with Enter.

4. On the Determain Work Area: Entry screen, enter the following data:

Usage B

Application EL

Field group 001



5. Choose Continue (Enter).

6. Choose New Entries (F5).

7. On the New Entries: Overview of Added Entries screen, enter the following data:

Field LLIEF



8. Choose Save.

3.1.1.1.2 Maintaining Condition Table

UseMaintain Condition Table for Scheduling Agreement Release/Expediter.

Since condition table is a DDIC object, it’s client independent. In certain circumstances, the condition table may already be generated, for example, if you have done this step in another client, If so, the system may reply with an error message: Request XXX belongs to a different client. Skip this step in this case.

Procedure


Transaction code M/62

IMG menu Materials Management Purchasing Messages Output Control Condition Tables Define Condition Tables for Scheduling Agreement Release / Expediter



2. On the Choose Activity screen, choose Create Condition Table: FRC Delivery Schedule/Expediter.

3. On the Create Condition Table (Output Purch. SchAgrRelease) screen, enter following entries:

Field name Description User action and values Note

Table 999

4. Confirm your entry.

5. On the Create Condition Table (Output Purch. SchAgrRelease): Field… screen, choose Purchasing org. On the right sub-screen, choose Select Field. The field Purchasing org. is displayed on the left sub-screen.

6. Repeat step 5 for Suppl. Vendor.

7. Choose Generate.

8. Save as local object.

3.1.1.1.3 Generating Condition Table 999

UseGenerate Condition Table 999 for Scheduling Agreement Release/Expediter.

Procedure


Transaction code M/63

IMG menu Materials Management Purchasing Messages Output Control Condition Tables Define Condition Tables for Scheduling Agreement Release / Expediter Display Condition Table: FRC Delivery Schedule/Expediter

2. Choose Condition Change from the menu.

3. On the Change Condition Table (Output Purch. SchAgrRelease) screen, make following entries:


Table 999

Table Description

Condition Table BP

JA description: Conditions tabelles BP



For maintaining German description, log on the system with log on language JA

4. Confirm your entry with Enter.

5. On the Change Condition Table (Output Purch. SchAgrRelease): Field… screen, choose Generate.

Since condition table is a DDIC object, it’s client independent. In certain circumstance, the condition table may already be generated, for example, you’ve done this step in other client, If so, the system may reply with an error message: Request XXX belongs to a different client. Skip this step in this case.

3.1.1.1.4 Maintaining Access Sequences

Use ATJK900241Maintain Access Sequences for Scheduling Agreement Release/Expediter.

Procedure


Transaction code SPRO

IMG menu Materials Management Purchasing Messages Output Control Access Sequences Define Access Sequence for Scheduling Agreement Release / Expediter



2. On the Change View Access sequences: Overview screen, choose New Entries.

3. On the New Entries: Overview of Added Entries screen, enter following entries:


Acsq Access sequence YAAF

Description DocType/PurchOrg/Vendor



4. Confirm your entry and select it.

5. On the left area of the screen, double-click the Access.

6. On the Change View Accesses: Overview screen, choose New Entries.



AcNo Accesses 4

Tab Table 999



8. Confirm your entry and select it.

9. On the left area of the screen, double-click Fields.

10. On the Change View Fields: Overview screen, choose New Entries.


Condition Doc.struc. Doc. Field Long Field label

EKORG KOMKBEA EKORG Purch. Organization

LLIEF KOMKBEA LLIEF Supplying vendor



12. Confirm your entry and Save.

3.1.1.1.5 Maintaining Output Types

UseOutput type YAH1 Forecast Delivery Schedule, and YAJ1 JIT Delivery Schedule, are copied from standard output types LPH1 and LPJ1. New output type YAJ3, is created for External Service Provider.

Procedure



IMG menu Materials Management Purchasing Messages Output Control Message Types Define Message Types for Scheduling Agreement Release / Expediter Maintain Message Types for Forecast Delivery Schedule/Expediter



2. Choose Output Type LPH1 and Copy As… (F6), then enter the following data:

Field name User action and values

Output Type YAH1

Description ForecastDlv Schedule

General data

CannotBeChanged Blank

Default values

Dispatch time 4 (Send immediately (when saving the application))



3. Choose Enter and Copy all.

4. Choose output type YPH1, select Processing routines, and enter the following data:

Field name User action and values User action and values

Output Type YAH1 YAH1

Application EL EL

Medium 1 (Print output) 2 (Fax)

Form MEDRUCK MEDRUCK

SmartForm Blank Blank



5. Choose Save.

6. Choose LPJ1 and Copy, then enter the following data:


Output Type YAJ1

Description JIT Delivery Sched.

Default Values

Dispatch Time 3 (Send with application own transaction)



7. Choose Enter then choose Copy all.

8. Choose YAJ1, select Processing routines, and enter the following data:


Output Type YAJ1 YAJ1

Application EL EL






9. Choose Save.

10. Choose LPJ1 and Copy, enter the following data:


Output Type YAJ3

Description JIT Dely Sched. EDL

General Data

Access Sequence YAAF


Default Values


Partner Function GS




12. Choose YPJ3, select Processing routines, and enter the following data:


Application EL EL






13. Choose YPJ3, select Partner roles and delete all the entries.

14. Choose YPJ3, select Partner roles, New Entries, and enter the following data:

Application EL

Output Type YAJ3

Medium EDI

Function GS (Goods supplier)



15. Choose Enter and choose Save.

16. Change request:

3.1.1.1.6 Defining Message Type for Summarized JIT Call

UseDefine the message types for summarized JIT calls. Message types represent various message contents, such as EDI and forms for printing in the summarized JIT call.

Procedure


Transaction code OJIN3

IMG menu Logistics Execution JIT Outbound Message Determination Define Message Type for Summarized JIT Call



2. Choose output type LPH1 and Copy As… (F6), then enter the following data:

Output Type YAH1


General data


Default values







Application EL EL






5. Choose Save.


Output Type YAJ1


Default Values







Application EL EL






9. Choose Save.


Output Type YAJ3


General Data

Access Sequence ZZAF


Default Values


Partner Function GS






Application EL EL






13. Choose YPJ3, select Partner functions, and delete all the entries.

14. Choose YPJ3, select Partner functions, New Entries, and enter the following data:

Application EL

Output Type YAJ3

Medium 6 (EDI)





3.1.1.1.7 Fine-Tuned Controlling

UseFine-Tuned Control: Forecast Delivery Schedule/Expediter

Procedure



IMG menu Materials Management Purchasing Messages Output Control Message Types Define Message Types for Scheduling Agreement Release / Expediter Fine-Tuned Control: Forecast Delivery Schedule/Expediter



2. Choose 9, LPH1 and A, LPJ1 and Copy, and enter the following data:

Print Operation 9 A

Condition Type YAH1 YAJ1

Update Print-Dependent Data X X



3. Choose Save.

4. Choose A, LPJ1 and Copy, and enter the following data:

Print Operation A

Condition Type YAJ3

Update Print-RelatedData X



5. Choose Save.

6. Change request:

3.1.1.1.8 Message Determination Schema

UseAccording to the new output types, a new message determination schema is defined.

Procedure



IMG menu Materials Management Purchasing Messages Output Control Message Determination Schemas Define Message Schema for Scheduling Agreement Release / Expediter Define Message Determ. Schema: Forecast Delivery Schedule/Expediter



2. Choose RMBEL1 and Copy, revise the following data:

Procedure YABEL1

Description Purchasing Sched.Line




4. Choose YABEL1select Control data, and enter the following data:

Procedure YMBEL1

Step Condition Counter Condition Type Requirement Manual Only

60 1 YAJ1 111 Blank

80 1 YAH1 109 Blank



5. Choose New Entry to insert one step:

Procedure YMBEL1


75 0 YAJ3 111 Blank



6. Choose step 100 and delete entry.

7. Choose Save.

8. Change request.

3.1.1.1.9 Assigning Schema to Scheduling Agreement Release/Expediter

UseAssign Schema to Scheduling Agreement Release/Expediter.

Procedure



IMG menu Materials Management Purchasing Messages Output Control Message Determination Schemas Define Message Schema for Scheduling Agreement Release / Expediter Assign Schema to Scheduling Agreement Release/Expediter



2. Choose B, EL, RMBEL1 and revise to the following data:

Usage B

Application EL

Procedure YABEL1



3. Choose Save.

3.1.1.2 Maintaining Output Determination for Billing Documents


UseOutput type YD03 is copied from RD00. New output types YAH1 to YAH4 are created for billing documents.

Procedure


Transaction code V/40

IMG menu Sales and Distribution Basic Functions Output Control Output Determination Output Determination Using the Condition Technique Maintain Output Determination for Billing Documents Maintain Output Types



2. Choose RD02 and Copy, and enter the following data:

Output Type YA02

Description Invoice VDA

Default Values

Dispatch Time 4 (Send immediately (when saving the application))




4. Choose YA02, select Processing routines, and enter the following data:

Output Type YA02 YA02

Application V3 V3

Medium 1 (Print output) 6 (EDI)

Program RLB_INVOICE RSNASTED

FORM Routine ENTRY EDI_PROCESSING

Form Blank Blank

SmartForm ZSD_INVOICE_SUPP Blank



5. Choose Save.


Output Type YA03

Description Invoice VDA

Default Values





8. Choose YA03, select Processing routines, and enter the following data:

Output Type YA03 YA03

Application V3 V3

Medium 1 (Print output) 6 (EDI)

Program RLB_INVOICE RSNASTED

FORM Routine ENTRY EDI_PROCESSING

Form Blank Blank

SmartForm ZSD_INVOICE_SUPP Blank



9. Choose Save.


Output Type YAH1

Description Invoice

General Data

Multiple Issuing X

Default Values





12. Choose YAH1, select Processing routines, and enter the following data:

Output Type YAH1 YAH1 YAH1 YAH1

Application V3 V3 V3 V3

Medium 1 (Print output) 2 (Fax) 6 (EDI) A (Distribution (ALE))

Program RLB_INVOICE RVADIN01 RSNASTED RSNASTED

Form Blank RVINVOICE01_GG Blank Blank

SmartForm LB_BIL_INVOICE Blank Blank Blank



13. Choose Save.

14. Choose YAH1and Copy, and enter the following data:

Output Type YAH2

Description Invoice





Output Type

YAH2 YAH2 YAH2 YAH2





SmartForm ZSD_INVOICE_SUPP Blank Blank Blank



17. Choose Save.

18. Choose YAH1 and Copy, and enter the following data:

Output Type YAH3

Description Invoice





Output Type

YAH3 YAH3 YAH3 YAH3



Program RLB_INVOICE RLB_INVOICE RSNASTED RSNASTED

Form Blank Blank Blank Blank

SmartForm ZSD_INVOICE_SUPP ZSD_INVOICE_SUPP Blank Blank



21. Choose Save.

22. Choose YAH1 and Copy, and enter the following data:

Output Type YAH4

Description Invoice





Output Type

YAH4 YAH4 YAH4 YAH4





SmartForm ZSD_INVOICE_SUPP Blank Blank Blank



25. Choose Save.

3.1.1.2.2 Maintaining Output Determination Procedures

UseAccording to the new output types, a new output determination procedure is defined.

Procedure



IMG menu Sales and Distribution Basic Functions Output Control Output Determination Output Determination Using the Condition Technique Maintain Output Determination for Billing Documents Maintain Output Determination Procedures



2. Choose New Entries, and enter the following data:

Usage B B

Application V3 V3

Procedure YA1000 YA1001

Description Billing Output Billing Output



3. Choose YA1000, select Control data, choose New Entries and enter the following data:

Procedure Y10000


10 1 RD00 62 Blank

20 2 MAIL Blank X

50 0 YA02 Blank Blank

60 0 FEEX Blank Blank

65 0 FEEV Blank Blank

70 0 FEEU Blank Blank

75 0 FEEA Blank Blank

80 0 FECO Blank Blank

90 0 FET1 Blank Blank

100 0 FET2 Blank Blank

110 0 FETR Blank Blank

111 0 FJCI Blank Blank

112 0 FJCO Blank Blank

113 0 FJCT Blank Blank

114 0 FJEP Blank Blank

115 0 FJER Blank Blank

120 0 JRMF Blank Blank

130 10 YAH1 Blank X

135 10 YAH2 Blank X

140 10 YAH3 Blank X

145 10 YAH4 Blank X

150 10 YA03 Blank X



4. Choose Save.


Procedure YA1001


10 1 RD00 62 Blank

20 2 MAIL Blank X

50 1 YA03 62 Blank



6. Choose Save.

3.1.1.2.3 Assigning Output Determination Procedures

Use Assign new output determination procedure to billing documents type.

Procedure



IMG menu Sales and Distribution Basic Functions Output Control Output Determination Output Determination Using the Condition Technique Maintain Output Determination for Billing Documents Assign Output Determination Procedures



8. On the Change View Billing Document Types – Output Determination: Overview screen, make the following entries:

Field name User actions and values

Billing document types YAF1

Output Procedure YA1000

Output type YAH3

Billing document types YAF2

Output Procedure YA1000

Output type YAH3



9. Choose Save.

3.1.1.3 Maintaining Output Determination for Outbound Deliveries


UseOutput type YANO, YALE, YAVA are copied and revised from CANO, LALE, and LAVA. New output type, such as YASA, YAV1, YD01, YAT1-YAT3, YWH1-YWH5, are created for outbound deliveries.

Procedure



IMG menu Logistics Execution Shipping Basic Shipping Functions Output Control Output Determination Maintain Output Determination for Outbound Deliveries Maintain Output Types



2. Choose CANO, LALE, LAVA and Copy, and enter the following data:

Output Type YANO YALE YAVA

Description Forwarding Notific. ShipNotifctn to SP Outg. Ship.notifica.

Default Values

Dispatch Time

4 (Send immediately (when saving the application))






4. Choose Save.

5. Choose LAVA and Copy, and enter the following data:

Output Type YASA

Description Outg. Ship.notif. DI

Default Values





7. Choose Save.

8. Choose LAVA and Copy, and enter the following data:

Output Type YAV1

Description Outg. Ship.notif.EDL



9. Choose Enter and only copy entry.

10. Choose Save.

11. Choose LD01 and Copy, and enter the following data:

Output Type YAD1 YAD2

Description Delivr Note DIN4994 Delivr Note DIN4994

Default Values


3 (Send with application own transaction)




13. Choose YD01 and YD02, select Processing routines, and enter the following data:

Output Type YAD1 YAD2

Application V2 V2

Medium 1 (Print output) 1 (Print output)

Form Blank Blank



14. Choose Enter and Save.

15. Choose New Entries, enter the following data:

Output Type YA00

Description Material Tags 4902/3

General Data

Access Sequence 0005

Access to Conditions X

Default Values


Transmission Medium 1 (Print output)

Partner Function SH (Ship-to party)

Print

Print Parameter 5 (Shipping point)



16. Choose Enter then choose YA00, select Mail title, and enter the following data:

Application V2

Output Type YA00

Language EN

Title Material Tags 4902/3



17. Choose Enter and output type YA00. Select Processing routines, and enter the following data:

Output Type YA00

Application V2

Medium 1 (Print output)

FORM Routine ENTRY

Form Blank



18. Choose Enter then choose YA00, select Partner function, enter the following data:

Application V2

Output type YA00


Function SH (Ship-to party)




20. Choose YA00 and Copy, and enter the following data:

Output Type YA01 YA02 YA03

Description Material Tags 4902/3 Material Tags 4902/3 Material Tags 4902/3



21. Choose Copy All and Save.

22. Choose YA01, YA02, YA03, select Processing routines, and enter the following data:

Output Type YA01 YA02 YA03

Application V2 V2 V2

Medium 1 (Print output) 1 (Print output) 1 (Print output)

Form Blank Blank Blank





Output Type YAT1 YPT2 YAT3

Description Material Tags 4902/3 Material Tags 4902/3 Material Tags 4902/3




26. Choose YAT1, YAT2, YAT3, select Processing routines, and enter the following data:

Output Type YAT1 YAT2 YAT3

Application V2 V2 V2

Medium 1 (Print output) 1 (Print output) 1 (Print output)

Program ZPTRVADWAHN_P005_A02

ZPTRVADWAHN_P005_A02

ZPTRVADWAHN_P005_A02

SmartForm ZSF_SD_MAT_LABEL_HU

ZSF_SD_KLT_LABEL_HU ZSF_SD_KLT_LABEL_HU





Output Type YAH1 YAH2 YAH3 YAH5 YAH7

Description Delivery Note

Delivery Note

Delivery Note Delivery Note

Delivery Note




30. Choose YAH1, YAH2, YAH3, YAH5, YAH7, select Processing routines, enter the following data:

Output Type

YAH1 YAH1 YAH2 YAH2 YAH3 YAH3 YAH5 YAH5 YAH7 YAH7

Application

V2 V2 V2 V2 V2 V2 V2 V2 V2 V2


2 (Fax)

1 (Print output)

2 (Fax)

1 (Print output)

2 (Fax)

1 (Print output)

2 (Fax)

1 (Print output)

2 (Fax)

Program SDADDN02

SDADDN02

RLE_DELNOTE

RLE_DELNOTE

RLE_DELNOTE

RLE_DELNOTE

/SMB05/RVADSPAT_P001_A02

/SMB05/RVADSPAT_P001_A02

ZSF_RVADSPAT_P008_A02

ZSF_RVADSPAT_P008_A02

Form SD_DELNOTE_SUPPL

SD_DELNOTE_SUPPL

Blank Blank Blank Blank Blank Blank Blank Blank

SmartForm

Blank Blank LE_SHP_DELNOTE

LE_SHP_DELNOTE

ZSD_DELNOTE_SUPP

ZSD_DELNOTE_SUPP

ZSD_FREIGHT_SUPP

ZSD_FREIGHT_SUPP

ZSD_FREIGHT_SUPP

ZSD_FREIGHT_SUPP





Output Type YAH4

Description Delivery Note DIN4994





Output Type YAH4

Application V2


Form Blank

Smart Forms ZSD_DELNOTE_SUPP





Output Type YAHA YAHB YAHC YAHD

Description Material Tags 4902/3

Material Tags 4902/3






38. Choose YWHA, YWHB, YWHC, YWHD, select Processing routines, and enter the following data:

Output Type

YWHA YWHB YWHC YWHD

Application

V2 V2 V2 V2

Medium 1 (Print output) 1 (Print output) 1 (Print output) 1 (Print output)

Program /SMB05/SF_SDADPL01_HU_P010_A02

/SMB05/SF_SDADPL01_HU_P010_A02

/SMB05/SDADPL01_P006_A02

/SMB05/SDADPL01_P006_A02

Form Blank Blank Blank Blank

SmartForm

LE_SHP_DELNOTE ZSF_SD_KLT_LABEL_HU

ZSF_SD_MAT_LABEL_HU

ZSF_SD_KLT_LABEL_HU




40. Choose WABS and Copy, and enter the following data:

Output Type YABS

Description Bond note

Default Values




41. Choose Enter and YABS. Select Mail title, and enter the following data:

Application V2

Output Type YABS

Language EN

Title Bond note



42. Choose Enter then choose YABS, select Processing routines, enter the following data:

Output Type YABS

Application V2


Program ZSF_RVADWABS_P009_A02

FORM Routine ENTRY

SmartForm ZSF_WABS_CONNOTE_SUPPL




44. Choose YABS and Copy, and enter the following data:

Output type YAHE

Description Bond note



45. Choose YAHE, select Processing routines, and enter the following data:

Output Type YAHE

Application V2


Program ZSF_RVADWABS_P009_A02

FORM Routine ENTRY

SmartForm ZSF_WABS_CONNOTE_SUPPL




3.1.1.3.2 Maintaining Output Determination Procedures

UseAccording to new output types, a new output determination procedure is defined.

Procedure



IMG menu Logistics Execution Shipping Basic Shipping Functions Output Control Output Determination Maintain Output Determination for Outbound Deliveries Maintain Output Determination Procedures



2. Choose New Entries, and enter the following data:

Usage B

Application V2

Procedure YA0001

Description Header Output - Automotive


Procedure Y10001

Step Condition Counter Condition type Requirement Manual Only

10 0 YAVA Blank Blank

15 0 YASA Blank Blank

20 0 YABS Blank Blank

40 0 YAD1 Blank Blank

45 0 LD00 Blank Blank

48 0 YAD2 Blank Blank




60 0 YALE Blank Blank

70 0 YANO Blank Blank

71 0 YAT1 Blank Blank



80 0 PL00 Blank Blank

90 0 YAV1 Blank Blank

102 0 YAH2 Blank Blank





108 0 YAHA Blank Blank

109 0 YAHB Blank Blank

110 0 YAHC Blank Blank

111 0 YAHD Blank Blank

112 0 YAHE Blank Blank



4. Choose Save.

3.1.1.3.3 Assigning Output Determination Procedures

UseAssign new output determination procedure to document type.

Procedure



IMG menu Logistics Execution Shipping Basic Shipping Functions Output Control Output Determination Maintain Output Determination for Outbound Deliveries Assign Output Determination Procedures Assign deliveries (header)



2. Revise the following data:

Delivery Types YALF LO

Output Procedure YA0001 YA0001

Output Type YAVA YAD1



3. Choose Save.

3.1.1.3.4 Changing Output Procedure for ASN

Procedure



IMG menu Logistics Execution Shipping Basic Shipping Functions Output Control Output Determination Maintain Output Determination Procedure for Outbound Deliveries Maintain Output Determination Procedure



2. Select Procedure YA0001; choose Control Data.

3. On the Change View Control Data: Overview screen, make the following entries:

Procedure YA0001

Step Condition Counter Condition type Requirement Manual Only

10 0 YAVA 1



4. Choose Save.

3.1.1.4 Maintaining Inbound Process Code

UseUpdate function model for inbound process code DELS.

Procedure


SAP ECC menu Tools ALE ALE Development IDoc Inbound Processing Define Process Code

Transaction code WE42



2. Choose Display Change (Ctrl+F1).

3. Select inbound process code DELS, Choose Details (F2).

4. On the Change View Inbound Process Code: Details screen, choose ALE table.

5. On the Change View Function Modules for inbound ALE-EDI: Details screen, make the following data:

Process Code DELS

Function Module /SPE/IDOC_INPUT_DESADV1



6. Choose Save.

3.1.1.5 Maintaining Outbound Process Code

UseUpdate function model for inbound process code YD05.

Procedure


SAP ECC menu Tools ALE ALE Development IDoc Outbound Processing Define Process Code




2. Choose Display Change (Ctrl+F1)

3. Choose New Entries,

4. On the New Entries: Detail for Added Entries screen, enter the following data:

Process Code YD05

Function Module IDOC_OUTPUT_DESADV01

Description EDI Outbound: Shipping Notification (DESADV)



5. Double-click logical Message.

6. On the New Entries: Detail for Added Entries screen, enter the following data

Process Code YD05

Message Type DESADV

Message Code

All Code X

Message Function

All Function X

Message Type EDLNOT

Message Code

Message Function



7. Choose Save.

8. Choose Back.

3.1.2 Partner Profile, Only Basic Data

UsePartner profiles for EDI communication are created at the supplier side.

Procedure


SAP ECC menu Logistics Logistics Execution JIT Outbound Environment Idoc/EDI Basis Administration Partner profile




2. On the Partner profiles screen, select Partner profiles Partner type LS.

3. Choose Create.

4. On the right top area of Partner profiles screen, make following entry:

Field name Description User action and values

Note

Partner Number

for example: RDDCLNT064

Supplier Logical System Name

The system assigns this number if you create a master record in an application (for example, purchasing, sales). The EDI partner is identified uniquely via the partner number and partner type.

If you define your own partner types, they are also identified by this number.



5. On the Partner profiles screen, select Post processing: permitted agent.

6. Make the following entries:

Field name

Description User action and values

Note

Typ Agent type US Agent type

Classifies the recipient of error notifications.

Examples

'US': An individual agent is notified.

‘O’: Agent type is an organizational unit: all persons assigned to this organizational unit are notified.

Dependencies

Individual persons are assigned to the positions, organizational units etc. in the PD Organizational Model (PD-ORG).



Field name

Description User action and values

Note

Agent AM-MUSTER Permitted users: ID

Specifies the job (person or group of people) to be notified if processing errors occur on the IDoc interface. You can define up to three different jobs:

In the inbound or outbound partner profiles for special partners, messages and direction.

In the general partner profiles for special partners.

In the general IDoc Administration settings.

Use

If an error occurs, only one (the most specific) job is notified. If an error occurs in the ORDERS message for partner HUGH, the system first attempts to determine whether a job responsible for ORDERS and HUGH is defined. If this is not the case, the job defined for HUGH (required entry) is notified.

The IDoc administrator is notified if HUGH does not exist at all in the partner profiles.

Examples

If the recipient type is 'US' ('user'), enter the name of the SAP user who is to be notified.

If the recipient type is 'O' ('organizational unit'), enter the organizational unit whose personnel are to be notified.

Dependencies

This specification depends on how you have configured the PD Organizational Model (PD-ORG).

Lang. Language of notification

EN If an error occurs, SAPoffice notifies the permitted user in this language.



7. Choose Save.

If the partner already exists, you can change the partner or choose a different customer.

If the customer number doesn’t exist in your system, an error message pops up: Enter a permitted partner number.

8. Repeat step 1- 7 for the following data.

Partner type Partner Number Type Agent Language

LS <RDDCLNT063> US AM-MUSTER EN



Enter your own OEM logical system name in the field Partner Number, for example, ET6CLNT100.

ResultPartner profile is created successfully.

3.1.3 Partner Profile Inbox

UseInbound parameters in partner profile are created at the supplier side.

Procedure






2. On the Partner profiles screen, select Partner profiles Partner type LS <OEM Logical System NameRDDCLNT063>,

3. On the Partner profiles screen, choose Insert under Inbound parmtrs.

4. On the Partner profiles: Inbound parameters screen, make the following entries:


Note

Partn. funct. Partner function of sender

As an optional parameter, the partner function containing the sender and the recipient can be specified. Example: 'LF' for 'vendor' or 'AG' for 'sold-to party'.

SNDPFC, SNDPRN and SNDPRT provide a unique ID for the sender. They are among the key fields in the partner profiles, which are used in inbound processing, for example, to determine the process code and therefore the internal processing for the IDoc. Therefore, if the sender function has been specified in the inbound partner profiles, the external system must maintain the field with the corresponding value.

Message type SBWAP In EDI, message types are normally assigned to SAP document types uniquely. Their names correspond as much as possible to those of the UN/EDIFACT standard. ALE scenarios, on the other hand, often have no EDIFACT correspondence, for example when master data is transmitted.

Example

ORDERS for purchase order data

INVOIC for invoice data



5. On the bottom area of the Partner profiles screen: Inbound parameters, select Inbound options tab.



Process code Inbound Process Code

SBAP The IDoc interface uses the process code to find the business process, which controls the conversion of the IDoc into the SAP document.

Syntax Check If you select the syntax check, the IDoc Interface terminates the processing if a syntax error is found.

If you do not select the syntax check, the IDoc Interface continues the processing. You receive a message that a syntax error was found.

Trigger Immediately

X The inbound IDoc is processed immediately.



7. Choose Save.

8. Repeat step 1 - 7 to enter the following entries:

Partner type

Partner Number

Message Type

Partner function

Message Code

Process code

Trigger immediately

Trigger by background program

LS

<OEM Logical System NameRDDCLNT063> ACCSTA ACCS X

LS

<OEM Logical System NameRDDCLNT063> DELFOR DELI X

LS

<OEM Logical System NameRDDCLNT063> DELJIT DELI X

LS

<OEM Logical System NameRDDCLNT063> DELFOR DELI X

LS

<OEM Logical System NameRDDCLNT063> DESADV DELS X

LS

<OEM Logical System NameRDDCLNT063> GSVERF MM SHPM X

LS

<OEM Logical System NameRDDCLNT063> INVOIC INVL X

LS

<OEM Logical System NameRDDCLNT063> INVOIC MM INVL X

LS

<OEM Logical System NameRDDCLNT063> PROACT PRAC X

LS

<OEM Logical System NameRDDCLNT063>

REMADV REMA X



Partner type

Partner Number

Message Type

Partner function

Message Code

Process code

Trigger immediately

Trigger by background program

LS

<OEM Logical System NameRDDCLNT063> SBINV SJCL

X

LS

<OEM Logical System NameRDDCLNT063> SEQJIT DLCN

X

LS

<OEM Logical System NameRDDCLNT063> SHPADV SHPM

X

LS

<SUP Logical System NameRDDCLNT064> DELCON DLCN

X

LS

<SUP Logical System NameRDDCLNT064> INVOIC INVL

X

LS

<SUP Logical System NameRDDCLNT064> INVOIC FI INVL

X

LS

<SUP Logical System NameRDDCLNT064> SEQJIT DLCN

X



Enter your own OEM or Supplier logical system name in the field Partner Number, for example, ET6CLNT100 or ET6CLNT103.

3.1.4 Inbound Function Module

UseWe need additional entries in Inbound Function Module table for EDI.

Procedure


SAP ECC menu Tools Business Communication IDoc Basis Development Message/Application Objects

Tools ALE ALE Development IDoc Inbound Processing Function Module Assign IDoc Type and Message Type




2. On the Display View screen, choose Change.

3. Choose New Entries.

4. Make following entries:

Module Type Basic type

Message Type

Message Code

Object type

Direction

IDOC_INPUT_DELINS_START

F DELFOR02

DELFOR

BUS2035 2


F DELFOR02

DELFOR

SDO BUS2035 2


F DELFOR02

DELJIT BUS2035 2


F DELFOR02

DELJIT SDO BUS2035 2

IDOC_INPUT_INVOIC_MRM

F INVOIC02 INVOIC BUS2081 2

IDOC_INPUT_INVOIC_MRM

F INVOIC02 INVOIC MM BUS2081 2



5. Choose Save.

3.1.5 Creating Message Output for Outline Agreement

UseIn this step, message condition master data for Outline Agreement output is created.

Varaint LU and LPA in conflict with Baseline variant SMB15_MN07_O322_J05_104.TXT.

Variant YLUC doesn’t exist in system.

Procedure


SAP ECC menu Logistics Material Management Purchasing Master Data Messages outline agreement Create

Transaction code MN07



2. On the Create Output – Condition Records: outline agreement screen, make the following entries:


Output type NEU



3. Choose Key Combination.

4. Confirm the dialog box by selecting Purchasing Output Determination: Document Type.



Document type LU

Partner Function VN

Medium 1

Time 3



6. Choose Communication.

7. On the Create Output – Condition Records: outline agreement: Communication screen, make the following entries:


Output device LP01



8. Choose Save.

9. Repeat steps 1-6 to enter following entries:

Output Type Doc. Type Partner Function Medium Time

NEU YLUC VN 1 3

NEU LPA VN 1 3



3.1.6 Maintaining tRFC Port

3.1.6.1 Maintaining a tRFC Port

UseA port is a group of technical attributes of a communication channel. This is required for dispatching messages to logical systems

Procedure


SAP ECC menu Logistics Logistics Execution JIT Outbound Environment Idoc/EDI Basis Administration Port difinition




2. On the Ports in IDoc processing screen, choose the Transactional RFC folder in the tree structure.

3. Choose Create.

4. In the dialog box displayed, choose Own port name. Enter the port name Z_AUTO_S.

5. On the Creating a tRFC port screen, enter the following information:


Description tRFC Port BP Automotive Supplier

RFC destination f RDDCLNT064 Supplier Logical System Name



The RFC destination here should enter the destination this client is to communicate, for example, you should enter the RFC destination of the relevant Supplier client.

6. Choose Save.

7. Choose Back.

8. On the Ports in IDoc processing screen, choose the Transactional RFC folder in the tree structure.

9. Choose Create.

10. In the dialog box displayed, choose own port name. Enter the port name Z_AUTO.

11. On the Creating a tRFC port screen, enter the following information:


Description tRFC Port BP Automotive OEM

RFC destination RDDCLNT063 OEM Logical System Name



The RFC destination here should enter the destination this client is to communicate, for example, you should enter the RFC destination of the relevant Supplier client.

12. Choose Save.

ResultA port is created in system successfully.

3.1.7 Maintaining a File Port

UseA port is description of the channel used by the SAP system for communicating with the external system during electronic data interchange. For Example: most EDI subsystems read IDocs in the form of sequential files, that is, the port type File is used.

In this section you can define the file port. This is required for dispatching messages to logical systems.

The port is assigned to a partner system in the partner profile.

Procedure



IMG menu Basis Components Application Link Enabling Sending and Receiving Systems Systems in Network Asynchronous Processing Assigning Ports Define Port



2. On the Ports in IDoc processing screen, select Ports File on the left area of screen.

3. Choose Create.

4. On the right area of Ports in IDoc processing screen, make following entries:


Port Port Name YEDIFILE

Description Automotive EDI File Port

Version IDoc record types SAP Release 4.x

5. On the right bottom area of Ports in IDoc processing screen, select Outbound file tab.



Physical directory

The file is uniquely identified via the directory (path) and their names.

/usr/sap/ RDD/SYS/global/

for example: /usr/sap/ET6/SYS/global/

D:\usr\sap\ATJ\SYS\global\

for example: under the UNIX operating system,

/usr/sap/ET6/SYS/global/

Under the Windows operating system:

\\sapdevdb\sapmnt\ET6\SYS\global\

Do not forget the last slash, as the file name is simply appended as a directory! In the example ET6 is the name of the SAP system.

Function Module

EDI_PATH_CREATE_USERNAME

In order to prevent unprocessed files being overwritten, you use function modules which generate file or directory names dynamically, that is to say, at runtime.

For the output value every function module must deliver a "complete file name", that is, a character string from directory and file names. The file system then operates with these complete names.

You can change the function module as you wish. To get all possible function modules, select F4 Help



You can choose Access Test to check the access permit to the folder you defined.

7. On the right bottom area of Ports in IDoc processing screen, select Inbound file tab.


Field name

Description User action and values Note

Physical directory

The file is uniquely identified via the directory (path) and their names.

/usr/sap/RDD/SYS/global/ When system automatically proposes a directory, do not change the system proposal.

for example: \\PWDF2756\sapET6root\usr\sap\ET6\SYS\global\

Inbound file

Inbound Here you can specify a fixed name for the file, in which the IDocs from external systems (for example EDI subsystem) are transferred. SAP however recommends that the external system starts the inbound processing in the R/3 System and notifies what the transferred file is called (Parameter from startrfc). The field is then ignored.

In general SAP recommends using dynamic file names, that is, variable file names generated at runtime, in order to prevent the overwriting of non-processed files.



9. On the right bottom area of Ports in IDoc processing screen, select Status file tab.



Physical directory

The file is uniquely identified via the directory ("path") and their names.

/usr/sap/RDD/SYS/global/

D:\usr\sap\ATJ\SYS\global\

When system automatically proposes a directory, do not change the system proposal.

for example: \\PWDF2756\sapET6root\usr\sap\ET6\SYS\global\

Status file Status Here you can specify a fixed name for the file, in which the status records from external systems (for example EDI subsystem) are transferred. SAP however recommends that the external system starts the status processing in the R/3-System and notifies what the transferred file is called (Parameter from startrfc). In this case the field is ignored.

In general SAP recommends using dynamic file names, that is to say variable file names generated at runtime, to prevent the overwriting of non-processed files.



11. Choose Save.

ResultA file port is created in system successfully.

3.1.8 Activating IDoc Inbound

UseRun a program to activate IDoc Inbound Processing.

This is one-time event, only need to be done once. If the system IDoc Inbound is already active, this step can be skipped.

Procedure


SAP ECC menu Tools ABAP Workbench Development ABAP Editor

Transaction code SE38



2. On the ABAP Editor: Initial Screen, run program RSEINBEV.

3. Choose Execute.

4. In the dialog box, select Yes.

ResultA successful message is displayed in the status bar IDoc: Event-event receiver coupling activated successfully.

3.1.9 EDI Invoice Parameters

3.1.9.1 Maintaining Program Parameters

UseAssign the selected company code to the name that your EDI partner uses for your company in the invoice.

Procedure


Transaction code OBCE

IMG menu Material Management Logistics Invoice Verification EDI Enter Program Parameters






Partn. type LS

Partn. number RDDCLNT063 OEM Logical System Name

Company Code 1000

Invoice doc. type RE

Cred.memo doc. type KG



4. Choose Save.

ResultThe program parameters have been created.

3.1.10 Creating Message: Sales and Distribution YANO

UseMessage condition master data for Sales and Distribution YANO is created.

Procedure


SAP ECC menu Logistics Sales and Distribution Master Data Output Shipping Create

Transaction code VV21



2. On the Create Output – Condition Records: Shipping screen, make the following entries:


Output type YANO



3. Choose Key combination.

4. Confirm the dialog box.



Shipping point 1000

Partner Function CR

Medium 6

Time 4



6. Choose Save.

3.1.11 Number Range

3.1.11.1 Creating Transmission Number Range for SD Self-billing

UseCreate Transmission Number Range for SD Self-billing.

Procedure


Transaction code ORLNI

IMG menu Materials Management Returnable Packaging Logistics Number Ranges Define Number Ranges for Internal EDI Transmission Numbers



2. On the EDI Internal Transfer Number screen, choose Change Intervals.

3. On the Maintain Number Range Intervals screen, choose Insert interval (SHIFT+F1).

4. On the Insert Interval screen, make the following entry:


No 01

From number 000000000001

To number 999999999999

Ext Blank



5. Choose Save.

3.2 Configuration in the OEM System

3.2.1 Output Determination

3.2.1.1 Maintaining Output Determination for Scheduling Agreement Release

3.2.1.1.1 Maintaining Output TypesThe Maintaining Output Types settings in the OEM system are the same as those in the Supplier system.

Refer to 3.1.1.2.1: Maintaining Output Types in the Supplier system.

Use ATJK900339Output type YPH1 Forecast Delivery Schedule, and YPJ1 JIT Delivery Schedule, are copied from standard output types LPH1 and LPJ1. New output type YPJ3, is created for External Service Provider.

Procedure



IMG menu Materials Management Purchasing Messages Output Control Message Types Define Message Types for Scheduling Agreement Release / Expediter Maintain Message Types for Forecast Delivery Schedule/Expediter



2. Choose Output Type LPH1 and Copy As… (F6), then enter the following data:


Output Type YAH1


General data


Default values








Application EL EL






5. Choose Save.



Output Type YAJ1


Default Values







Output Type YPJ1 YAJ1 YPJ1 YAJ1

Application EL EL






9. Choose Save.



Output Type YAJ3


General Data



Default Values


Partner Function GS






Application EL EL






13. Choose YPJ3, select Partner roles and delete all the entries.

14. Choose YPJ3, select Partner roles, New Entries, and enter the following data:

Application EL

Output Type YAJ3

Medium EDI





3.2.1.1.2 Defining Message Type for Summarized JIT CallThe Defining Message Types for Summarized JIT Call settings in the OEM system are the same as those in the Supplier system.

UseDefine the message types for summarized JIT calls. Message types represent various message contents, such as EDI and forms for printing in the summarized JIT call.

Procedure


Transaction code OJIN3

IMG menu Logistics Execution JIT Outbound Message Determination Define Message Type for Summarized JIT Call



2. Choose output type LPH1 and Copy As… (F6), then enter the following data:

Output Type YAH1


General data


Default values







Application EL EL






5. Choose Save.


Output Type YAJ1


Default Values







Application EL EL






9. Choose Save.


Output Type YAJ3


General Data



Default Values


Partner Function GS




12. Choose YAJ3, select Processing routines, and enter the following data:


Application EL EL






13. Choose YPJ3, select Partner functions, and delete all the entries.

14. Choose YPJ3, select Partner functions, New Entries, and enter the following data:

Application EL

Output Type YAJ3

Medium 6 (EDI)





3.2.1.1.3 Fine-Tuned ControllingThe Fine-Tuned Controlling settings in the OEM system are the same as those in the Supplier system.

Refer to 3.1.1.1.3Fine-Tuned Controlling in the Supplier system.

UseFine-Tuned Control: Forecast Delivery Schedule/Expediter

Procedure



IMG menu Materials Management Purchasing Messages Output Control Message Types Define Message Types for Scheduling Agreement Release / Expediter Fine-Tuned Control: Forecast Delivery Schedule/Expediter



2. Choose 9, LPH1 and A, LPJ1 and Copy, and enter the following data:

Print Operation 9 A

Condition Type YAH1 YAJ1

Update Print-Dependent Data X X



3. Choose Save.

4. Choose A, LPJ1 and Copy, and enter the following data:

Print Operation A

Condition Type YAJ3

Update Print-RelatedData X



5. Choose Save.

3.2.1.1.4 Message Determination SchemaThe Message Determination Schema settings in the OEM system are the same as those in the Supplier system.

UseAccording to the new output types, a new message determination schema is defined.

Procedure



IMG menu Materials Management Purchasing Messages Output Control Message Determination Schemas Define Message Schema for Scheduling Agreement Release / Expediter Define Message Determ. Schema: Forecast Delivery Schedule/Expediter



2. Choose RMBEL1 and Copy, revise the following data:

Procedure YABEL1

Description Purchasing Sched.Line




4. Choose YABEL1select Control data, and enter the following data:

Procedure YABEL1


60 1 YAJ1 111 Blank

80 1 YAH1 109 Blank



5. Choose New Entry to insert one step:

Procedure YMBEL1


75 0 YAJ3 111 Blank



6. Choose step 100 and delete entry.

7. Choose Save.

3.2.1.1.5 Assigning Schema to Scheduling Agreement Release/Expediter

The Assigning Schema to Scheduling Agreement Release/Expediter settings in the OEM system are the same as those in the Supplier system.

UseAssign Schema to Scheduling Agreement Release/Expediter.

Procedure



IMG menu Materials Management Purchasing Messages Output Control Message Determination Schemas Define Message Schema for Scheduling Agreement Release / Expediter Assign Schema to Scheduling Agreement Release/Expediter



2. Choose B, EL, RMBEL1 and revise to the following data:

Usage B

Application EL

Procedure YABEL1



3. Choose Save.

3.2.1.2 Maintaining Output Determination for Logistics Invoice Verification

The Maintaining Output Determination for Logistics Invoice Verification settings in the OEM system are the same as those in the Supplier system.

3.2.1.2.1 Maintaining Message Types

UseOutput type ERS6, is modified from standard output type ERS6.

Procedure


Transaction code M806

IMG menu Materials Management Logistics Invoice Verification Messages Determination Maintain Message Types



2. Choose ERS6, and enter the following data:

Output Type ERS6

Description ERS Procedure EDI

General Data

Access Sequence 0002

Default Values


Partner Function VN (Vendor)



3. Choose Save.

3.2.1.3 Maintaining Inbound Process CodeThe Maintaining Inbound Process Code settings in the OEM system are the same as those in the Supplier system.

UseUpdate function model for inbound process code DELS.

Procedure


SAP ECC menu Tools ALE ALE Development IDoc Inbound Processing Define Process Code




2. Choose Display Change (Ctrl+F1).

3. Select inbound process code DELS, Choose Details (F2).

4. On the Change View Inbound Process Code: Details screen, choose ALE table.

5. On the Change View Function Modules for inbound ALE-EDI: Details screen, make the following data:

Process Code DELS

Function Module /SPE/IDOC_INPUT_DESADV1



6. Choose Save.

3.2.2 Activating Requirement 111 for Output Control

UseThe requirement 111 is not activated by default in standard system. As a result, the output of MM delivery schedule is incorrect.

Procedure


Transaction code VOFM



2. On the Maintain: Requirements & Formulas screen, choose from menu Requirements Output Control.

3. On the Maintain: Requirements Output control, choose routine number 111.

4. Choose from menu Edit Activate.

5. On the Prompt for local Workbench request screen, assign or create your own local workbench request.

3.2.3 Partner Profile, Only Basic Data

UsePartner profiles for EDI communication are created at the OEM side.

Procedure






2. On the Partner profiles screen, select Partner profiles Partner type LS.

3. Choose Create.

4. On the right top area of Partner profiles screen, make following entry:


Partner Number

for example: RDDCLNT064 Supplier logical system name

The system assigns this number if you create a master record in an application (for example, purchasing, sales). The EDI partner is identified uniquely via the partner number and partner type.

If you define your own partner types, they are also identified by this number.



5. On the Partner profiles screen, select Post processing: permitted agent.



Typ Agent type US Agent type

Classifies the recipient of error notifications.

Examples

'US': An individual agent is notified.

‘O’: Agent type is an organizational unit: all persons assigned to this organizational unit are notified.

Dependencies

Individual persons are assigned to the positions, organizational units etc. in the PD Organizational Model (PD-ORG).




Agent AM-MUSTER Permitted users: ID

Specifies the job (person or group of people) to be notified if processing errors occur on the IDoc interface. You can define up to three different jobs:

In the inbound or outbound partner profiles for special partners, messages and direction.

In the general partner profiles for special partners.

In the general IDoc Administration settings.

Use

If an error occurs, only one (the most specific) job is notified. If an error occurs in the ORDERS message for partner HUGH, the system first attempts to determine whether a job responsible for ORDERS and HUGH is defined. If this is not the case, the job defined for HUGH (required entry) is notified.

The IDoc administrator is notified if HUGH does not exist at all in the partner profiles.

Examples

If the recipient type is 'US' ('user'), enter the name of the SAP user who is to be notified.

If the recipient type is 'O' ('organizational unit'), enter the organizational unit whose personnel are to be notified.

Dependencies

This specification depends on how you have configured the PD Organizational Model (PD-ORG).

Lang. Language of notification

EN If an error occurs, SAPoffice notifies the permitted user in this language.



7. Choose Save.

If the partner already exists, you can change the partner or choose a different customer.

If the customer number doesn’t exist in your system, an error message pops up: Enter a permitted partner number.

ResultPartner profile is created successfully.

3.2.4 Partner Profile Inbox

UseInbound parameters in partner profile are created at the OEM side.

Procedure






2. On the Partner profiles screen, select Partner profiles Partner type LS <Supplier Logical System Name>, RDDCLNT064.

3. On the Partner profiles screen, choose Insert under Inbound parmtrs.

4. On the Partner profiles: Inbound parameters screen, make the following entries:


Partn. funct. Partner function of sender

As an optional parameter, the partner function containing the sender and the recipient can be specified. Example: 'LF' for 'vendor' or 'AG' for 'sold-to party'.

SNDPFC, SNDPRN and SNDPRT provide a unique ID for the sender. They are among the key fields in the partner profiles, which are used in inbound processing, for example, to determine the process code and therefore the internal processing for the IDoc. Therefore, if the sender function has been specified in the inbound partner profiles, the external system must maintain the field with the corresponding value.

Message type

CARNOT In EDI, message types are normally assigned to SAP document types uniquely. Their names correspond as much as possible to those of the UN/EDIFACT standard. ALE scenarios, on the other hand, often have no EDIFACT correspondence, for example when master data is transmitted.

Example

ORDERS for purchase order data

INVOIC for invoice data



5. On the bottom area of the Partner profiles screen: Inbound parameters, select Inbound options tab.



Process code

Inbound Process Code

APLI The IDoc interface uses the process code to find the business process, which controls the conversion of the IDoc into the SAP document.

Syntax Check

X If you select the syntax check, the IDoc Interface terminates the processing if a syntax error is found.

If you do not select the syntax check, the IDoc Interface continues the processing. You receive a message that a syntax error was found.

Trigger Immediately

X The inbound IDoc is processed immediately.



7. Choose Save.

8. Repeat steps 1-7 to enter the following entries:

Partner Type

Partner Number

Message Type

Partner Function

Message Code

Process Code

Syntax Check

Trigger Immediately

LS RDDCLNT064 DELORD DELO X X

LS RDDCLNT064 DESADV DELS X X

LS RDDCLNT064 INVOIC INVL X X

LS RDDCLNT064 INVOIC MM INVL X X

LS RDDCLNT064 REMADV REMA X X

LS RDDCLNT063 DELFOR DELI X X

LS RDDCLNT063 DELJIT DELI X X

LS RDDCLNT063 DESADV DELS X X



Enter your own Supplier logical system name in the field Partner Number, RDDCLNT064

Enter your own OEM logical system name in the field Partner Number, RDDCLNT063

ResultPartner profile inbox is created successfully.

3.2.5 Maintaining a tRFC Port

3.2.5.1 Maintaining a tRFC Port

UseCreate tRFC Port for OEM/ESP.

Procedure


SAP ECC menu Logistics Logistics Execution JIT Outbound Environment Idoc/EDI Basis Administration Port difinition




2. On the left area of the screen Ports in IDoc Processing, choose Ports Transactional RFC.

3. Choose Create.

4. In the dialog box, enter Own Port Name: Z_AUTO.

5. On the right top area of Ports in IDoc Processing screen, make the following entries:


Note

Description Automotive - Supplier

Version IDoc Record types SAP release 4.x

RFC Destination

RDDCLNT064 Supplier Logical System Name

Make a change of the value KD7CLNT116 to your own corresponding logical system name. Usually the name convention of the logical system is system number (3 chars) + ‘CLNT’ + Client (3 Chars), here we need the client of your OEM/ESP. for example if you system is SD7 and client of Supplier is 116, then the value here should be changed to SD7CLNT116.



6. Choose Save.

3.2.5.2 Assigning Tax Code

UseAssign tax parameters for legal requirement.

Procedure


Transaction code OBCD

IMG menu Material Management Logistics Invoice Verification EDI Assign Tax Codes



2. On the Change View: EDI: conversion of external tax rate tax code overview screen, make the following entries:

Field name Sub Screen User action and values Note

Partner type LS

Partner No. RDDCLNT064 Supplier Logical System Name

Tax type VAT

Tax rate 5.000 Do not miss the zero

Tax code V1

3. Choose Save and choose Back.

3.2.6 EDI Invoice Parameters

3.2.6.1 Maintaining Program Parameters

UseAssign the selected company code to the name that your EDI partner uses for your company in the invoice.

Procedure


Transaction code OBCE

IMG menu Material Management Logistics Invoice Verification EDI Enter Program Parameters




Partn. type LS

Partn. number RDDCLNT064 Supplier Logical System Name

Company Code 1000

Invoice doc. type RE

Cred.memo doc. type KG

4. Choose Save.

ResultThe program parameters have been created.
