0% found this document useful (0 votes)
152 views82 pages

Intercompany Process

Intercompany Process

Uploaded by

Monica
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
152 views82 pages

Intercompany Process

Intercompany Process

Uploaded by

Monica
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 82

InterCompany Billing - Automatic Posting To Vendor Account (SAP-EDI) in SAP

S/4HANA

Automatic posting to vendor account is done by EDI. In our case where both companies
are processed in the same system (& client), it is sufficient to create Idoc.

This process requires several steps:

1. Creating a Customer to represent the receiving Company (customer).


2. Creating a Vendor to represent the supplying company (supplier).
3. Creating a Port
4. Maintain an Output Type
5. Creating a Logical Address
6. Creating a Partner Profile for both Customer & Vendor
7. The relevant MM customizing is maintained.
8. The relevant FI customizing is maintained.

1. Creating a Customer to represent the receiving Company

The customer has already been created (BP) for the purpose of Intercompany processing
and entered in the appropriate transaction in customizing (Sales and Distribution 

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

1|Page
Billing  Intercompany Billing  Define Internal Customer Number By Sales
Organization).

Define Internal Customer Number By Sales Organization

In this menu option, you assign an internal customer number for intercompany billing to your sales
organization. In intercompany billing, the intercompany billing document is created for this customer
number which represents your sales organization. The intercompany billing document is assigned via
the internal customer number of your sales organization.

Actions

1. Create a customer number that represents your sales organization.


2. Enter this customer number for the corresponding sales organization.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

2|Page
Note: The customer has been created in the supplying company code. The organizational
data in this case is:
Supplying Company Code: 1032
Supplying Plant: 1032
Supplying Sales Organization: 1032
Supplying Distribution Channel: 90
Supplying Division: 10

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

3|Page
Receiving Company Code: 1010
Customer representing the receiving Company Code: 1010

2. Creating a Vendor to represent the supplying company.


The Vendor is created with the standard transaction (BP).
Note: The Vendor is created in the receiving Company Code. The organizational data in
this case is the same as above.

Vendor representing the supplying Company Code: 1032

NOTE: There is NO need to “connect” vendor to customer in the control screen.

3. Creating a Port
Tools  Business Communication  IDoc Basis  Idoc  Port Definition
(T. Code WE21)

Maintain Transactional RFC: (Choose Transactional RFC and press the create icon). A
dialog box will open asking whether you want the system to generate an automatic
name or whether you wish to use your own name.

Port name: Automatically generated


Version: 4.x
RFC destination: PLD (This was defined by the basis people).

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

4|Page
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

5|Page
4. Maintain output type

Output Type RD04 - Invoice Receipt MM is a special function, responsible for the
execution of the IDOC and will be entered in the Partner Profile later on.

Output type RD04 is maintained: Img: Sales and Distribution  Basic functions 
Output control  Output Determination  Output Determination Using the Condition
Technique  Maintain Output Determination for Billing Documents  Maintain Output
Types (T. Code V/40).

Maintain Output Types

Use

In this step, you define the output types for output type records.

The output type represents different output, such as quotations, order confirmations, and delivery notes
in the system.

Note that when multiple address handling is enabled, you must specify the form type as PDF and
maintain the appropriate program, form routine, and PDF form name accordingly to print the address in
the output.

For more information about multiple address handling for business partners in sales and distribution
and how to enable it, see Multiple Address Handling Using SAP Business Partner.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

6|Page
To define an output type, make the following entries:

• Output type

alphanumeric key with up to four characters to identify the output condition

• Access sequence

access sequence key

• Description

text describing the output type

• Detailed data (only the most important data is listed here):

o Output type

one-digit, numeric key which defines the type of output processing (for example,
printout, message sent by telefax or mail)

o Time

one-digit, numeric key which defines the time of output processing (for example,
immediately when saving a document or during the next selection run)

o Partner function

partner function for defining the recipient of an output in the sales & distribution
document

o Condition access

indicator which controls whether the output is to be proposed using the condition
technique
If you do not set the indicator, the system finds the output using the proposal in the
customer master record. However, you must first set the corresponding defaults for
output determination from the customer master record.

o Print parameters

One-digit, numeric key which defines the requirements on the basis of which the print
parameters are defined (see the section "Define print parameters").

o Archiving mode

This field controls whether a document is only printed, only archived or both printed
and archived.

o Archiving object type

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

7|Page
This field identifies the archived outputs and determines whether it is an invoice,
quotation, etc. The archiving object type of the incoming document begins with SDI,
the archiving object type of the outgoing document begins with SDO.

Note

The values entered for output type, time and partner function for the detail data are automatically
transferred as default values when creating a condition record by output condition.

Recommendation

• To create a new output type, copy a similar access sequence in the system and make the
necessary changes.

• If you define your own output types, the key should begin with the letter Y or Z

Actions

1. Check to what extent you can use output types contained in the standard system and to
what extent you must change them.
2. Define output types for all SD documents.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

8|Page
Details

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

9|Page
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

10 | P a g e
Mail title and texts

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

11 | P a g e
Processing routines

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

12 | P a g e
Partner functions

Sales and Distribution  Basic Functions  Output Control  Output Determination 


Output Determination Using the Condition Technique  Maintain Output Determination
for Billing Documents

Assign Output Types To Partner Functions

Assign Output Types To Partner Functions

In this step, you assign the allowed output types to partner functions.

In addition, you can specify the allowed type of output processing for the combination of output types
and partner functions.

Requirements

First define output types.

Actions

Specify a previously defined output type. Specify the allowed partner functions. Define an output
medium (for example, printout, telefax, or mail).

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

13 | P a g e
Maintain Output Determination Procedure

Maintain Output Determination Procedure

In this step, define output determinations for documents.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

14 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

15 | P a g e
Assign Output Determination Procedures

Assign Output Determination Procedures

In this menu option, assign output determination procedures to the documents.

You may also specify an output type which is to be displayed when the relevant document is displayed
or changed.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

16 | P a g e
Master Data

Maintain output Master Data

Logistics  Sales and Distribution  Master Data  Output  (T. Code VV31)
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

17 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

18 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

19 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

20 | P a g e
5. Create Logical Address
Img: Sales and Distribution  Billing  Intercompany Billing  Automatic Posting To
Vendor Account (SAP-EDI)  Assign vendor. (T. Code WEL1)

Automatic Posting To Supplier Account (SAP-EDI)

In this activity, you set up automatic posting to supplier account for intercompany billing with SAP-EDI
direct to financial accounting.

EDI outbound processing for intercompany billing links to EDI inbound processing for invoice receipt in
FI and posting to supplier account is carried out in the selling company code.

prerequisites:

Before making the settings in Customizing you must create a supplier master record that represents the
delivering company code. This supplier master record must be created in "Selling company code".

You also need an output condition record (transaction VV31) for output type "RD04" and the customers
for intercompany billing.

Customizing settings:

1. Message type:

Message type RD04 is set for posting to supplier account in intercompany billing. (TA:V/040)

2. Message determination procedure:

Message determination procedure V40000 is valid for billing type IV.

3. Message control:

In the administration of EDI processing, a partner agreement must be defined for message control of
inbound and outbound processing, since sender and receiver data are needed. The outbound process
code is used to initiate a function module version 5 (function module version 3.0 for initiating inbound
processing).

Process code outbound: SD08.

For further information on settings for messages, see the Customizing section "messages".

4. Outbound processing:
a) Partner agreement (transaction WE20)
Partner number : Specify customer number IV
Partner type : KU
b) Message controlling:
Partner number : Customer number IV
Partner type : KU
Partner role : RE
Application : V3
Message type :RD04
Message:
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

21 | P a g e
Message category:INVOIC
Message variant: FI
Outbound options:
Outbound code : SD08 INVOIC Intercompany billing,
c) Outbound parameters:
Outbound options:
Receiver port : e.g. SAPP30 EDI MM development
IDoc cat. : INVOIC01
Basis IDoc cat. : INVOIC01
5. Inbound processing (transaction SBPT) for customer
a) Inbound parameters:
Partner number : Specify supplier number
Partner type : LI
Partner functions:
Message category : INVOIC invoice / billing document
Output variant : FI
Process code :INVF
6. Check assignment of process code and processing function modules.
Transaction: WE42 >>Basis >> Control>> Process code inbound >> Processing with funct.
modules>>With or w/o ALE
Code :INVF
Identification:idoc_input_invoice_fi (INVOIC FI invoice receipt)
or
code FI03 up to 3.0E
Identification:idoc_input_invoice_fi
7. Supplier:
A supplier must be assigned per company code and customer for intercompany billing
(transaction WEL1)

Example:
Data:
Delivering company code: 0001
Customer: 0000000001, created in delivering company code
Selling company codekreis: 0099
Supplier: ALECRED01, created om selling company code

Settings:
Application: V3
Logical address 00010000000001
is made up of:
a) 4 place delivering company code : 0001
b) 10 place customer number : 0000000001

Target:
Company code: 0099
Supplier : ALECRED01

Note

The logical address must contain 14 digits. If the customer number does not contain 10 digits, zeros
must be put before it.

If the logical address is not correctly maintained in table EDILOGADR, error message: " Company code
could not be determined for intermediate document XXXXX" appears.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

22 | P a g e
8. Account assignment:

You can set an indicator that determines whether account assignments are to be copied from the
customer billing document during creation of posting to supplier account in the selling company code

This affects the following account assignments:

9. Projects
10. Profit center
11. Cost center
12. Profitability segment
13. Business area
a) Partner Profit Center (delivering profit center)

The same settings must be made for the internal credit memo.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

23 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

24 | P a g e
Logical address 10320000001010 is made of the supplying Company Code (1032) and the
receiving Customer (0000001010).

Note: If the receiving Customer is a numeric number, you must add zeros between the
Company code and Customer number so the Logical Address will be 14 digits.
E.g if the customer number was 1009, than the logical address would have been
10320000001009 as can be seen in the second line. (In our case the customer is an alpha
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

25 | P a g e
numeric number so the second line was not necessary. It was created just for this
documentation and was not saved)

The Logical address is completed when the receiving Company Code 1010 and the
Vendor 1032 are entered in the detail screen.

It is also necessary to activate the account assignment.

Img: Sales and Distribution  Billing  Intercompany Billing  Automatic Posting To


Vendor Account (SAP-EDI)  Activate account assignment.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

26 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

27 | P a g e
6. Creating a Partner Profile for both Customer & Vendor
Tools  Business Communication  IDoc Basis  Idoc  Partner Profile (T. Code
WE20)

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

28 | P a g e
Customer:
Put cursor on Partner type KU and press create.
Enter typ, Agent & Lang,
SAVE

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

29 | P a g e
Press in outbound paratrs. Section, to maintain detail screens

The following screen will appear.

Enter the following data in the appropriate fields:

Partn.funct. BP
Message type INVOIC
Message Code FI
Receiving port A000000001
Basic Type INVOIC01
Press enter and the screen will change to the following:

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

30 | P a g e
Enter PaketSize 1

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

31 | P a g e
Go to the Message Control tab press and enter the data as specified in the following
screen

You can repeat the process for cases where invoice verification is done against purchase
order. in this case enter MM in “message code field.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

32 | P a g e
Vendor

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

33 | P a g e
As you can see the only difference between the FI & MM invoice is in the message code
and output type.

NOTE: You cannot use output type RD04 again therefore you must copy it in customizing
to another output type (in this case RD00)

FI CUSTOMIZING

Financial Accounting  Accounts Receivable and Accounts Payable  Business


Transactions  Incoming Invoices/Credit Memos  EDI  Enter Program Parameters
for EDI Incoming Invoice (T. Code OBCE)

Enter Program Parameters for EDI Incoming Invoice

Use

For each EDI partner and invoice company code, you enter parameters for the content and the
procedure, which determine how the EDI invoices are posted in the system.

Make the following entries for the posting procedure:

• Posting key for the debit posting and the credit posting to the G/L account or the vendor
account.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

34 | P a g e
• Document types for credit memos and invoices

• Clearing accounts

An EDI invoice with more than 949 posting items is distributed to more than one FI document.
If you only require a vendor posting, you can temporarily post the additional documents to the
specified clearing account.

• Tax code for tax-exempt items

This tax code is used for posting surcharges and reductions that affect the whole invoice, and
for posting split clearing lines.

You enter the following for transfer flags:

Calculate tax

If you select this field, the system calculates the tax. Otherwise, it uses the tax that is specified
in the EDI invoice.

• Transferred tax jurisdiction code

If the tax jurisdiction code is transferred in the EDI invoice, select this field.

• Surcharges/reductions at header level

If surcharges or reductions are transferred in the EDI invoice header, select this field so that
the surcharges or reductions can be posted at totals level (segment E1EDK05).

You enter the following for processing:

• Park document

If you select this field, the document is only parked in Accounts Payable Accounting.
Otherwise, the document is posted there.

• BDC session

If you select this field, then the system creates a batch-input sesion when you park or post
documents. Otherwise, the EDI invoice is posted directly to Accounts Payable Accounting.
Note

o If an EDI invoice creates more than 949 posting lines, then more than one FI
document is created, and regardless of this setting, the system also creates a batch-
input session. This is because the system cannot ensure that the invoice is either
posted or posted completely when more than one single document is posted.

o If you use the transfer price function, the system always posts the document directly.

• Surcharge/reduction at totals level

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

35 | P a g e
If you select this field, surcharges or reductions that were determined on the invoice items are
displayed in separate document lines

Requirements

For more information, see: Introduction To EDI.

Enter the tax parameters for posting the EDI invoices and credit memos received,

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

36 | P a g e
Make sure to maintain posting types, tax code and invoice doc.type. Use KR when not
using purchase order & RE when using purchase order.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

37 | P a g e
Details

Assign Company Code for EDI Incoming Invoice

Assign Company Code for EDI Incoming Invoice

Use

For each EDI partner, you assign the company code (that contains the payable to be posted) to the
name for the invoice recipient in the EDI invoice.

Technical Note

The name is read from the NAME1 field in the E1EDKA1 segment for the invoice recipient (qualifier IR)
or the sold-to party (qualifier SP).

Requirements

You do not do this IMG activity, if the company code (in which the system posts the payable from the
EDI invoice) was determined in one of the following ways:

• The company code is read from the E1EDK14 segment with qualifier 011.

• You process an intercompany transaction and have already specified a sender (from which the
company code is determined) in Sales & Distribution customizing under Billing ->Intercompany
Billing -> Automatic Posting to Vendor Account (SAP-EDI) -> Assign Vendor.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

38 | P a g e
• The company code is determined using a customer exit, for example, EXIT_SAPLIEDI_001
(enhancement FEDI0001).

For more information on customer exits, see the following IMG activity:
Develop Enhancements for EDI Incoming Invoices.

For more information on general preqrequisites, see: Introduction to EDI.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

39 | P a g e
By leaving the field CoCD blank, all company codes are available.

Assign G/L Accounts for EDI Procedures (T. Code OBCB)

Assign G/L Accounts for EDI Procedures

Use

For each EDI partner and invoice company code (company code for the vendor), enter the G/L
account for the expense account posting or revenue posting and the company code to which the
expense account or revenue is to be assigned.

The G/L account for goods or services items is determined by the name of the good or service in the
EDI invoice. The G/L account for surcharges and price reductions is determined from the condition key
and the condition plus-minus sign (+ for surcharge, - for reduction).

If the company code for the G/L account differs from the invoice company code, then the system
creates a cross-company code posting.

Note
The leading company code is the company code from the first G/L account posting in the
document, not the company code from the vendor.

If you require additional functions to determine the G/L account and the company code, use the
following customer exit:

• Customer exit EXIT_SAPLIEDI_001

• Enhancement FEDI0001

For more information, see the IMG activity Develop Enhancements for EDI Invoice Receipt.

Requirements

For more information on general conditions, see Introduction to EDI.

Activities

1. Enter the EDI partner.


2. Enter the invoice company code.
3. Enter the goods or service number.
The following entries are possible:

o Goods or service name in the EDI invoice

o * for all goods or services not listed.

o Condition plus-minus sign and condition key for surcharge or reduction.

o + for all surcharges not listed.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

40 | P a g e
o - for all reductions not listed.

4. Enter the G/L account for the expense account posting or revenue posting.
5. Enter the company code to shich the expense or revenue is to be assigned.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

41 | P a g e
1032 = Vendor
1010 = Company Code of receiving company (of customer)

NOTE:

G/L account should not be connected to CO.


Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

42 | P a g e
Assign Tax Codes for EDI Procedures (T.Code OBCD)

It is necessary to match the output tax from the sales order to the input tax.

Tax type =
Outpu
t Tax
Tx =
Input
Tax

Assign Tax Codes for EDI Procedures

Use

For each EDI partner, you assign the tax code defined in the SAP System to the tax type and
the tax rate determined by that partner.

You can assign these according to the country/region of the invoice recipient (the country/region
of the company code) where the supplier account is located.

• If you want to make the assignment independently of the country/region, then leave
the Country/Region field empty.

• If you want to make the assignment independently of the tax type, then enter VAT as
the tax type. The tax code is determined on the basis of the tax rate.

Caution

The tax rate determined in the IDoc is compared character by character to those in the tax rate
that you enter here.

Example

0.1 does not equal 0.10000

0.1 does not equal 0,1

Requirements

For more information about general prerequisites, see Introduction to EDI.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

43 | P a g e
Accounting  Financial Accounting  General Ledger  Master Records  Individual
Processing  Centrally (T.Code FS00)

Manage G/L Account Master Data


With the transactional app Manage G/L Account Master Data, you can display, create and edit
the master data of G/L accounts. You can also easily add new G/L accounts from scratch or
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

44 | P a g e
based on existing accounts. In addition, the app provides you with options to mass change
account description and other attributes. This app is a Fiori UI5 app (F0731A), as a
replacement of the Web Dynpro app (F0731).

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

45 | P a g e
G/L account no. = account number that was entered in transaction OBCB (page 24) Tax
category must allow for input tax.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

46 | P a g e
Make sure manual posting is allowed for the G/L account. (“Create/Bank/Interest”
screen).

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

47 | P a g e
TEXT

In many cases the G/L account has been configured so that text is mandatory. This could
be either Header Text or Item Text.

Header Text
No special configuration is necessary. Just enter text in the “Header note”. You may use
the following access sequence.

Define and Assign Text Determination Procedures

Short text

Set up the rules used to perform text determination

Use

You can define the rules that should be used to perform text determination.

Prerequisites

Define text types for text objects.

Defining Access Sequences for Determining Texts

You can define access sequences to be used in a text determination procedure for the text object.
The access sequence defines how the system is to search for texts.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

48 | P a g e
Note

• You can define access sequences only for text objects in SD documents. There is no need to
define access sequences for customer master, because texts are not copied but manually
specified by users.

In each access sequence, you need to define the sequence and search requirements.

This allows you, for example, to have the system check whether a text exists in the customer language.
If this is not the case, the system can search for a text in the sales organization's language. If this is
also unsuccessful, you can have the system carry out the search in English.

You can make the following specifications for each access sequence:

• SeqNo (sequential access number within an access sequence)

You can define the order in which the text objects of an access sequence are read. The
element with the lowest access number is read first. If an appropriate text is found, the search
ends. Otherwise, the system checks the element with the next lowest access number.

• Text object

You can define which text objects are checked by the system for an access sequence.
In the standard system, for example, in the access sequence 0001 for the text object sales
document header, the system first searches for a form header text in the preceding document
(text object VBBK) and then for a sales note in the customer master record (text object KNVV).

• ID (text type)

You can define which text type is read from the specified text object.
It is recommended that you select the same text type for the source text and target text
involved in text determination. For example, the text for the sales note for customer (text type
0001) in the customer master record should be copied to the sales note for customer (text type
0001) of a sales document.

• Partner Function

For texts copied from a customer master record, you can define which partner function is
included in the text search.

• Original language

You can specify language requirements for the text to be copied:

o All Languages

The system copies texts regardless of language.

o Language

The system copies texts available in specified language.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

49 | P a g e
o Partner Function Language

The system copies texts available in the language of the specified partner.
For example, if you specify the partner function of the sold-to-party, the text is only
copied if it is available in the sold-to-party's language.

o Sales Organization Language

The system copies texts available in the sales organization's language.

Note

• Existing requirements are pre-delivered by SAP and refer to copying text from preceding
documents.

• For every text type, you must maintain separate access sequences.

The text types of a text object are grouped together in text determination procedures. You assign a
text determination procedure using certain keys, for example, account group customer or sales
document type.

Defining and Assigning Text Determination Procedures

You can define text determination procedures for the text object as follows:

• You select one of the text determination procedures, then you assign text types for the
selected text determination procedure. You must set the fields of the text type in text procedure
with the relevant values.

• For text objects in SD documents, you define the access sequences and assign text types to
these access sequences. You must set the fields of the access sequence for text type with the
relevant values.

When you are editing a customer master record of the assigned account group or a sales document of
the assigned document type, the system offers the text types of the corresponding text determination
procedure.

You can also change the following settings for each text type:

• Refer/Duplicate

You can specify whether a text is duplicated or referenced. If you select this option, the text is
duplicated. Otherwise, it is referenced.
If a text is duplicated, the system creates an independent copy of the text. You can change
either the source or target text without affecting the other.
If a text is referenced, it only exists once in the database. A change in the source text triggers a
concurrent change in the target text in the subsequent document. However, the system deletes
the reference once you change the target text.

• FGrp (error group)

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

50 | P a g e
Using the error group, you can mark texts as relevant for the incompletion log of the sales
documents. If a relevant text of this text type is missing in the sales document, a note is
included in the incompletion log.

• Text is obligatory

You can specify whether a text is mandatory, and whether the system displays the text when it
is copied (such as from the customer master record to a sales document).
Note that this setting only applies to Sales Document Header, Sales Document Item, and
Delivery Header.

Afterwards you assign the defined text determination procedures as follows:

Text Object Key


Customer master record Account group
Sales document header Sales document type
Sales document item Item category
Delivery header Delivery type
Delivery item Item category
Billing header Billing type
Billing item Billing type

Note

Currently you cannot set up your own error groups for the incompletion log for texts in customizing.

In the standard system, error group "50" is defined for texts. The incompletion log takes it into account if
the texts are additionally characterized as required in the procedure.

Requirements

You can only include text types in a procedure which you have defined beforehand.

• The account groups, document types, and item categories must already be defined. They are
then proposed to you automatically for assignment.

Actions

1. Check to what extent you can use the text determination procedures contained in the
standard system.
2. Change the existing text determination procedures according to your needs or create new
ones.
To do this, branch to the text determination procedures for a text object and display the texts in
the procedure.
3. Assign the text determination procedures.
There are two ways to do this:

o by calling up the text determination procedure assignment

Here, you can carry out the assignment for the selected text determination procedure.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

51 | P a g e
o by calling up text determination procedure usage

Here, the assignments are displayed for the account groups, the document types and
item categories.

Transport

To initiate transport, select 'Text - Transport' in the initial screen.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

52 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

53 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

54 | P a g e
Item Text
It is necessary to implement a userexit in order to fill the item text field. Detailed
instructions are found in note 39503

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

55 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

56 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

57 | P a g e
MM Customizing:

Make sure the Unit of Measure’s ISO Codes are configured correctly.

General Settings  Check units of measurement (T. Code CUNI)

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

58 | P a g e
Details

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

59 | P a g e
Optional MM Customizing:

NOTE: This is only necessary for logistics invoice verification.

Materials Management  Logistics Invoice Verification  EDI  Enter Program


Parameters

Enter Program Parameters

In this Customizing activity, you define the control parameters for posting incoming invoices sent via
IDoc.

Enter the following parameters:

In the Posting Information group box, specify the following:

• Which document type the system is to use when an invoice is sent via IDoc

• Which document type the system is to use when a credit memo is sent via IDoc

The other settings depend on whether you want to enter invoices received via IDoc in Invoice
Verification or in Differential Invoicing (you configure this in EDI Partner Profiles).

• Logistics Invoice Verification

Define how the system reacts when there are differences between the values received via
IDoc and the values proposed by the system. Enter the following in the Logistics Invoice
Verification only area:
Processing type
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

60 | P a g e
Blank:
The invoice document is posted using the invoice data. If the invoice contains quantity or price
variances, the system blocks it for payment.
1:
The invoice document is entered as containing unclarified errors and saved with the values
proposed by the system and the values contained in the IDoc invoice. You have to manually
process the parked invoice document later.
2:
The invoice document is posted with the values determined by the system. The IDoc invoice is
reduced by the amount of the variance.
3:
Depending on the positive small difference configured in the supplier-specific tolerances, the
invoice document is created as follows: The system first compares the positive small difference
tolerance limit with the total of the positive variances of the invoice items in an invoice. Positive
differences arise when the invoice value transmitted via IDoc is greater than the value
proposed by the system.

o If the positive difference is smaller than the positive small difference tolerance limit,
the invoice is posted with a quantity or price variance and the system blocks it for
payment.

o If the positive difference is greater than the positive small difference tolerance limit, the
invoice is parked as containing an unclarified error and you must process it manually.

4:
The invoice document is checked against the tolerances in accordance with online processing.
You maintain the tolerance keys on a company-code-specific basis and use them to determine
which variances are checked.

Checking material numbers and units of measure


Define whether the material numbers and units of measure in the IDoc invoice are to be
compared to those in the purchase order items. Note that the invoice cannot be posted if there
are variances.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

61 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

62 | P a g e
Details

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

63 | P a g e
RESULT

Manage Sales Orders


With this app, you as an internal sales representative can list all sales orders in the system,
filter the results, or search for specific sales orders. You can also create, change, or display
single sales orders containing key information in a fast and easy way. You can do so directly
within the Manage Sales Orders - Version 2 app, whereas in the Manage Sales
Orders app, you need to navigate to other apps.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

64 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

65 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

66 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

67 | P a g e
Create Billing Documents

With this app, you can create billing documents (for example, invoices and credit memos)
from items in the billing due list. This includes debit memo requests, sales orders, deliveries,
and other sales and distribution (SD) documents. You can also generate temporary billing
documents that you can review before converting them to final billing documents.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

68 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

69 | P a g e
Manage Billing Documents
With this app, you can manage invoices, invoice cancellations, credit memos, and other
billing documents. This includes displaying, editing, posting, and canceling billing documents.
You can also review why a billing document split has occurred and generate PDF-based print
previews of billing documents.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

70 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

71 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

72 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

73 | P a g e
Monitoring

There are several transactions that allow you to monitor the IDoc. First you need to know
the IDoc number. You can see the IDoc number in the processing log in the “Header
output” screen in the billing document.

You can use transaction WE02 or WE05. Enter the IDoc number in the selection screen.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

74 | P a g e
Bd87

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

75 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

76 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

77 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

78 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

79 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

80 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

81 | P a g e
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

82 | P a g e

You might also like