GU - SAP S4 HANA - 2338115 - Error Message E0332 - Complementary Information For SAP Note 31126

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 12

Mickael QUESNOT © https://s4hclub.

com/

Error message E0332 - Complementary information

“EDI: Partner profile not available - Message no. E0332

Diagnosis: A partner profile could not be found with the following key:

/0000000000/LI/”

1.1.1 Cause
The rootcause of this message usually is the missing entry in table EDILOGADR. In order to find
out which entry is missing, please check field BUKKRED.

Please find below an example. Put a breakpoint at the below function module:

************************************************************************
IDOC_OUTPUT_INVOIC_IV_MM
...
*- Faktura lesen
PERFORM LESEN_FAKTURA.
MOVE VBDKR-BUKRS TO BUKKRED(4).
MOVE VBDKR-KUNRE TO BUKKRED+4(10).
CLEAR EDILOGADR.
SELECT SINGLE * FROM EDILOGADR WHERE LOGADR = BUKKRED. SY-SUBRC=0
KNVV-EIKTO = EDILOGADR-DESTIN+4(10).

VBDKR-BUKRS 20
VBDKR-KUNRE 0000012345
BUKKRED 20 0000012345

************************************************************************

In this example a logical address 20 0000012345 is expected but not maintained in WEL1
transaction.
This address has to be connected to the vendor (KUNRE) and company code (BUKRS) of SAP
destination system.

1.1.2 Resolution
In transaction WEL1 or table EDILOGADR alphanumerical vendors have to be available without
leading zeros, whereas numerical vendor codes have to be available with leading zeros. These are
character fields which means space is also important.

The logical address should be the same as the value of field BUKKRED, in our example: ’20
0000012345’.

Mickaël QUESNOT © - Copyright

https://www.linkedin.com/in/mickaelquesnot/
1
Mickael QUESNOT © https://s4hclub.com/

EDI: Partner profile does not exist


Message no. E0332

Diagnosis
A partner profile could not be found with the following key:

/0000000000/LI/

This involves the key fields of the table EDPP1:

-PARNUM partner number


-PARTYP partner type

Procedure
Please check the EDI partner profiles.

Execute function

Mickaël QUESNOT © - Copyright

https://www.linkedin.com/in/mickaelquesnot/
2
Mickael QUESNOT © https://s4hclub.com/

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.

Mickaël QUESNOT © - Copyright

https://www.linkedin.com/in/mickaelquesnot/
3
Mickael QUESNOT © https://s4hclub.com/

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
Mickaël QUESNOT © - Copyright

https://www.linkedin.com/in/mickaelquesnot/
4
Mickael QUESNOT © https://s4hclub.com/

Partner type : KU
b) Message controlling:
Partner number : Customer number IV
Partner type : KU
Partner role : RE
Application : V3
Message type :RD04
Message:
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

Mickaël QUESNOT © - Copyright

https://www.linkedin.com/in/mickaelquesnot/
5
Mickael QUESNOT © https://s4hclub.com/

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.

8. Account assignment:

Mickaël QUESNOT © - Copyright

https://www.linkedin.com/in/mickaelquesnot/
6
Mickael QUESNOT © https://s4hclub.com/

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 © - Copyright

https://www.linkedin.com/in/mickaelquesnot/
7
Mickael QUESNOT © https://s4hclub.com/

Mickaël QUESNOT © - Copyright

https://www.linkedin.com/in/mickaelquesnot/
8
Mickael QUESNOT © https://s4hclub.com/

Mickaël QUESNOT © - Copyright

https://www.linkedin.com/in/mickaelquesnot/
9
Mickael QUESNOT © https://s4hclub.com/

Result

Mickaël QUESNOT © - Copyright

https://www.linkedin.com/in/mickaelquesnot/
10
Mickael QUESNOT © https://s4hclub.com/

IDoc '0000000000192030' was added and passed for output


Message no. E0045

Mickaël QUESNOT © - Copyright

https://www.linkedin.com/in/mickaelquesnot/
11
Mickael QUESNOT © https://s4hclub.com/

Mickaël QUESNOT © - Copyright

https://www.linkedin.com/in/mickaelquesnot/
12

You might also like