IDOCS - Instruction key
Hi
Experts,
In order to instruct the bank to print online the remittance advice for a vendor payment, special instructions need to be configured in SAP. This is done using instruction key configuration which is country and payment method specific.
But, When I do configure Instruction keys, The system is already showing Convert Instructiion Key. How to Define Instruction keys now?
Financial Accounting u2013 Accounts Receivable and Accounts Payable u2013 Business Transactions u2013Outgoing
Payments u2013 Payment Media u2013 Data Medium Exchange u2013 Define Instruction Keys.
Kindly suggest me in this case.
Anil
Hi
Friend,
I defined Instruction keys by 'Define Instructions for Payment Transactions'. But, when I went to Define instruction key path, it is showing me the screen Convert instruction key.
Anil
Similar Messages
-
Hello,
I had created few instruction keys and assigned them in the Vendor master. I was able to create an Idoc payment for the Vendor but, the instruction key information is not passed to the Idoc. Can someone advice me what I am missing on this?
Thank YouNot all fields of the vendor master record are necessarily passed to an IDoc. It is likely that you need to use a customer enhancement (aka u201Cuser exitu201D) to add the additional data in the segments that you need. Call upon your ABAP support folks.
Regards,
zKen -
How many instruction keys can we declare at the vendor bank details section?
I understand that if the vendor is being shared across company codes, the instruction key will be available to the relevant companies. If company A's instruction key is different from company B's instruction key, how do we accomodate both companies' instructions to the bank then?
Hi Ethan,
Instruction keys you can maintain in Vendor/Customer Master Record, general data section, and your question how we can accommodate by company code:
1. You can maintain Instruction Key in House Bank Master data, under Data Medium Exchange tab, T.Code FI12, which is company Code specific, in this way you can maintained company code wise different instruction keys. If the instruction key is not maintained in vendor/customer master data, then the default instruction key defined for the house bank is used.
2. You can also enter Instruction key at document level, in vendor/customer line item or it can be overwritten
Regards
Javed -
Instruction key in an invoice not taken
Hello!
I have a question concerning the instruction key.
I didnt define an instruction key in the vendor master data nor in the house bank.
And i dont want to define this instruction key in the master data, otherwise, it will come each time in the payment run.
Sometimes, we have to use the instruction key and sometimes not, that's why i dont want to define it in the master data.
But i define an instruction key in the invoice document for the vendor.
when i do the payment run, the instruction key of the invoice is not taken into account.
What should i do in order the system takes the insctuction key completed in the invoice document?
Thanks!
Kind regards,
ChiachenHi,
We have maintained the Instruction key in to vendor master and while downloading the by using the ACH for Canada, instruction key is missing.
Value is there in REGUH and not there in REGUP, how to get the same in to download file.
Help me on this issue.
Regards,
Satyam -
Instruction Key - Editable in Accounting Document
Guys
Can you help me with changing fields in Accounting document - i need to make instruction key editable.
Thanks!Hi,
Go to Path SPRO > Financial Accounting (New) > Financial Accounting Basic Settings (New) > Document > Rules for Changing Documents > Document Change Rules, Line Item and here add Instruction key (Field name as "BSEC-DTAWS") and Save.
Then try to change it in FB03. -
Dear all,
Please help me to fill data from field Instruction key form the vendor master data into DME. If the instruction key contains information in the vendor master data, how can this information be transferted into DME?
Thank you,
DesimiraHi,
You can take instruction key from the Master data. The key for this in DMEE is FPAYH-DTAWS (found in Source fields for Application -> Payment medium : payment data -> Payment medium : Instructions to Bank -> Instruction key for DME.
1. If the instruction key is maintained in the master record, then this instruction key is used.
2. If no instruction key exists in the vendor master record, then the default instruction key defined for the house bank is used.
Ravi. -
Hi all,
I have a question regarding payment runs. Is it always that the "Instruction Key" must be defined for payment runs.
Is this especially true in the case for Brazil?
Thanks
DInstruction key for data medium exchange
For automatic payment transactions, this field (along with the house bank country and the payment method determined by the payment program) controls which statements are given to the participating banks when carrying out the payment order. This field is used in countries such as Germany, Austria, the Netherlands, Spain, Norway, Finland, and Japan as well as for the internnational SWIFT format, MT100.
Selecting the instruction key
If data medium exchange is used (as well as in special cases when using document-based payment orders) the instruction key must be maintained in the customer/vendor master record, or in the system configuration for data medium exchange data for the house bank. The following holds regarding the instruction key:
1. If the instruction key is maintained in the master record, then this instruction key is used.
2. If no instruction key exists in the vendor master record, then the default instruction key defined for the house bank is used.
Consequently, it is not necessary to provide all business partners with an instruction key; only the exceptions need to be maintained.
Note 1
If it is necessary to specify an instruction key for a business partner's house bank that differs from the instruction key defined in the master record, this can be done when editing the payment proposal.
Note 2
The instruction key must be entered in the document for one-time accounts.
Note 3
The four instruction key fields belonging to the instruction key can be overridden by entering instruction keys in the document (the "Additional Data" screen in the customer or vendor line). -
Hello all,
I am getting confused with the instruction keys in OB47
I have defined
Bank Country : xxx
Payment method : 4
Instruction key : 01
and again we have payment medium instructions with list of
Instruction key 1
instruction key 2
instruction key 3
instruction key 4
what we have to do with these. i have read the help note, but did not understood it clearly.Dear,
please be aware that in IMG the path is:
Financial Accounting -> Accounts Rec. and Acc. payable -> Business
Transactions -> Outgoing Payments - > Automatic Outgoing Payments ->
Payment Media -> Data Medium Exchange -> Define Instruction Keys
Please check the documentation to this transaction.
Define Instruction Keys
In this activity you define an instruction key, which controls what
instructions for making a payment order are sent to participating banks.
You can specify the key in vendor master records or for house banks.
Activities
1. Find out what instructions for data medium exchange are to be
defined in the system.
2. Define these instructions in the system.
3. Make sure the key is defined for your house banks (standard entry)
or in the vendor master record.
I hope this helps You.
Mauri -
Fill IDOC segment, E1IDBW1. For PEXR2002 Basic Type
Hello Team.
We send the IDOC for the Basic Type PEXR2002, Message Type PAYEXT.
This IDOC doesn't fill the Segment E1IDBW1 (IDoc header - special instructions (INP) )
I'm review some notes(1164524) and said to fill this segment it's neccesarie config the IHC.
But doesn't have this functionality.
It's possible fill the segment E1IDBW1 in a user exit or any other enhacement at creation idoc moment?
My idea is used the FM
CALL FUNCTION 'GET_SEGMENT_POS_FOR_INSERT'
EXPORTING
I_BASIS_TYPE = ch_edidc-idoctp
I_EXT_TYPE = ch_edidc-cimtyp
I_SEGMENT_TYPE = 'E1IDBW1'
IMPORTING
E_INDEX = li_tabix
TABLES
IT_EDIDD = t_edidd
EXCEPTIONS
BASIS_TYPE_NOT_FOUND = 1
EXTENSION_NOT_FOUND = 2
EXTENSION_ERROR = 3
INVALID_IDOC_DEFINITION = 4
IDOC_ERROR = 5
INVALID_SEGMENT_TYPE = 6
INVALID_START_INDEX = 7
NO_MORE_POSITION = 8
TOO_MANY_SEGMENTS = 9
OTHERS = 10.
To Fill 2 constants in this segment.
Do you have any other idea?
Thanks
Edited by: David Lezama Gonzalez on Sep 1, 2011 2:51 PMHi,
Basically the segment E1IDBW1 will always be filled via user exit.
If you work with the IHC (In-House-Cash) application you have to fill
the E1IDBW1 segment as described in note 626577.
If you don't work in an IHC environment the following conditions must
be fulfilled:
1. The payment program has to fill certain fields (e. g. REGUH-DTAWS,
REGUH-DTWS1 - REGUH-DTWS4).
2. If this is fulfilled the payment data (REGUH, REGUP tables) will
be filled. The instruction keys will be moved to IDOC segment
E1IDKU3.
3. In user exit EXIT_SAPLIEDP_002 you can take over the instruction
keys from segment E1IDKU3 into E1IDBW1.
You may also read note 496663, this note explains about user exit
EXIT_SAPLIEDP_002 to populate this field in the idoc.
Also, you can check the note:
580321 - RFFOEDI1: BTE process 00002441 (Change IDoc)
REgards,
Cristiano -
Outbound IDOC for message type PAYEXT
Hi,
I am trying to send a IDOC from my SAP system to a EDI vendor. For one particular vendor in segment E1IDKU3 field PAIRZAWE (payment terms) is mot coming, thought this data is been maintained in Vendor Master Data.
In Segment E1IDKU4 field FCAREGUL is also missing for which also there is a data maintained in Vendor Master.
Can anybody explain why this is happening.
Also, which is the FM or IDOC creation-processing program for this message type.
/ManikHi Manik,
Your function module to process the IDOC will either be FI_EDI_PAYEXT_PEXR2001_OUT or FI_EDI_REMADV_PEXR2001_OUT depending on whether you are doing a remittance advice or payment advice.
In include LIEDPF1T, subroutine FORM FILL_SEGMENT_IDKU4 USING DOC_TYPE, you will find the following code. This tells me that your E1IDKU4 problem is also related to your instruction key settings. Check this table and see what is wrong.
IF NOT T015W IS INITIAL.
CASE T015W-DTKVS. "Gebührenregelung
WHEN '00'.
E1IDKU4-FCAREGUL = Q_FCA_GETEILT.
WHEN '01'.
E1IDKU4-FCAREGUL = Q_FCA_Z_PFICHTIGER.
WHEN '02'.
E1IDKU4-FCAREGUL = Q_FCA_Z_EMPFAENGER.
ENDCASE.
ENDIF.
If it helps, please reward and close the thread.
Srinivas
Message was edited by: Srinivas Adavi
By the way what is Sardinians? -
Further instructions on wire payments
I have configured SAP to generate an IDoc from the payment run that will automatically send the payment file to our bank in order to execute wires and ACH payments. Some vendors require further instructions on their wires. An example is that a company has all of their wires sent to one central account and then we have to put instructions of the wire as to what sub account it needs to go to. I don't see anywhere in SAP where I can enter those instructions and then have them included on the payment information that I am sending to the bank. Do you know of a way to do this?
Hi,
Check whether Instruction key defined in transaction code OB47 will be helpful. The path is as under:
SPRO > Financial Accounting > Accounts Receivable > Business Transactions > Outgoing Payments > Automatic Outgoing Payments > Payment Media > Data Medium Exchange > Define Instruction keys.
Thanks
Murali. -
Hi all,
I am doing a BPM for 1:n multimapping.
Start->receive idoc->Transformation->send asynchronous->Stop.
In the transformation, I have a source message and two target messages. I want to send this message as a single message to the receiving MQ system.
In the send asynchronous step after transformation, I can give only one message for sending. Can anyone suggest some solution for this?
Thanks in advance,
DenoHi,
If you follow Siva suggestion you will altering the XSD of the IDoc itself. I feel its better you enclose both messages in a separate root tag.
Also when merging, you should use Message Type XSD of your custom strcuture and not Data Type XSD of your custom structure.
The following is an example of a merged custom XSD and IDoc XSD:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="MergedMessage">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="resultset" type="resultset" />
<xsd:element name="CREMAS03">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="IDOC" type="CREMAS.CREMAS03"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="CREMAS03">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="IDOC" type="CREMAS.CREMAS03"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="CREMAS03.E1LFA1M">
<xsd:annotation>
<xsd:documentation>
Segment for general vendor data
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="MSGFN" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Function
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LIFNR" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Account number of vendor or creditor
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ANRED" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Title
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="BAHNS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Train station
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="25"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="BBBNR" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
International location number (part 1)
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="7"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="BBSNR" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
International location number (part 2)
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="5"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="BEGRU" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Authorization group
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="BRSCH" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Industry key
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="BUBKZ" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Check digit for the international location number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DATLT" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Data communication line no.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="14"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DTAMS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Report key for data medium exchange
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DTAWS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Instruction key for data medium exchange
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ERDAT" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Date on which the Record Was Created
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="8"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ERNAM" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Name of Person who Created the Object
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ESRNR" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
POR subscriber number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="11"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="KONZS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Group key
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="KTOKK" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Vendor account group
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="KUNNR" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Customer number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LAND1" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Country of company
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LNRZA" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Account number of vendor or creditor
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LOEVM" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Central Deletion Flag for Master Record
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NAME1" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Employee's last name
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NAME2" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Employee's last name
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NAME3" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Employee's last name
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NAME4" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Employee's last name
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ORT01" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
City
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ORT02" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
District
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PFACH" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
P.O. Box
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PSTL2" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Postal Code
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PSTLZ" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Postal Code
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="REGIO" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Region (State, Province, County)
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SORTL" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Character field length = 10
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SPERR" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Central posting block
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SPERM" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Centrally imposed purchasing block
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SPRAS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Language key
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STCD1" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Tax number 1
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="16"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STCD2" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Tax number 2
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="11"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STKZA" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Indicator: Business Partner Subject to Equalization Tax?
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STKZU" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Indicator: Business partner subject to tax on sales/purch. ?
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STRAS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
House number and street
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TELBX" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Telebox number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TELF1" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
First telephone number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="16"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TELF2" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Second telephone number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="16"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TELFX" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Fax number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="31"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TELTX" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Teletex number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="30"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TELX1" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Telex number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="30"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="XCPDK" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Indicator: Is the account a one-time account?
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="XZEMP" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Indicator: Alternative payee in document allowed ?
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="VBUND" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Company ID of trading partner
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="6"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="FISKN" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Account number of the master record with fiscal address
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STCEG" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
VAT registration number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STKZN" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Indicator: Is business partner a natural person?
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SPERQ" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Function That Will Be Blocked
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ADRNR" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Address
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MCOD1" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Search term for matchcode search
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="25"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MCOD2" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Search term for matchcode search
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="25"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MCOD3" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Search term for matchcode search
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="25"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GBORT" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Place of birth of the person subject to withholding tax
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="25"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GBDAT" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Date of Birth
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="8"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SEXKZ" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Key for the *** of the Person Subject to Withholding Tax
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="KRAUS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Credit information number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="11"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="REVDB" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Last review (external)
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="8"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="QSSYS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Vendor's QM system
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="KTOCK" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Reference Account Group for One-Time Account (Vendor)
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PFORT" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
PO Box city
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="WERKS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Plant
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LTSNA" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Indicator: vendor sub-range relevant
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="WERKR" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Indicator: plant level relevant
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PLKAL" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Factory calendar key
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DUEFL" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Status of Data Transfer into Subsequent Release
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TXJCD" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Jurisdiction for tax calculation - tax jurisdiction code
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SCACD" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Standard carrier access code
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SFRGR" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Forwarding agent freight group
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:rest -
Hi All,
Could some explain to me the use of the Business Partner on the IHC set up table IHC_DB_IHB_PARMS.
My understanding is that the Business Partner is you Business Partner Number created using transaction BP.
My configure for table IHC_DB_IHB_PARMS is as below:
Clearing Partner Debit/Credit Currency Company Code Account Type Business Partner G/L Account
FI H ZAR ZPPC S 400000000027 114472
FI S ZAR ZPPC S 400000000027 114472
When posting payment orders, I am getting status 51 with the following message:
"Account 40000000027 does not exist in company code. Message No. IHC000"
It looks like its using the Business Partner as a G/L account instead of the G/L Account 114472.
Could someone explain to me the difference between business partner & G/L Account.
is the Business Partner also dependent on the Account Type "S" - G/L Account?
Your explanations will be greatly appreciated.
Regards,
GodhelpThe table you are giving is IHC_DB_INB_PARMS. Please find below explanation of the set up.
Customization menu path in SPRO is as follows:
SPRO - Financial Supply Chain Management - In-House Cash - Account Management - Payment Processes in In-House Cash - Outgoing Payment Orders - Set Up Creation of Payment Requests for Inbound IDoc in FI
Set Up Creation of Payment Requests for Inbound IDoc in FI
Use
In this IMG activity you enter all settings for creating FI payment requests if incoming payment IDocs are forwarded from an IHC Center to FI for external payment with the F111 payment program.
Definition of the clearing partner
Define a corresponding entry to identify the clearing partner for each clearing partner permitted to send payment IDocs to FI for further processing by means of the F111 payment program.
a) Account details for a clearing partner
Enter account details (bank country, bank number, account number) and the sender type and number that a clearing partner transferred in the fields of the payment IDoc when payment orders were forwarded for processing with the F111 payment program (control record and segment E1IDB02 Qualifier 'BA').
b) Posting accounts for a clearing partner
Maintain the company code, partner account and partner account type for each clearing partner, dependent on the logical message PAYEXT (=> credit/debit indicator credit) or DIRDEB (=> credit/debit indicator debit). You can select G/L, customer or vendor accounts from the corresponding account type selection. The currency field is optional. It allows you to differentiate between company codes and accounts on the basis of the transaction currency.
c) Parameters for creating payment orders for a clearing partner
Maintain the payment method selection, the payment method supplement, the house bank group or the house bank account in the company code to be used for each clearing partner dependent on the payment currency, the payment method, the payment method supplement and instructions 1-4.
You can also specify, when a debit memo is forwarded to FI for external payment, whether or not it should be presumed that the clearing partner has permission to debit the drawee and if this is to be treated in the same way as your own permission to debit the drawee.
You can also define whether or not a payment request should be created with a payment block, meaning that it always has to be explicitly released for payment, or if a certain instruction key should be used.
The payment currency, payment method, payment method supplement and instructions 1-4 are optional and allow you to differentiate between the parameters in more detail on the basis of data supplied in the payment IDoc.
Hope you will get clarity from this.
Kind Regards,
Chandra Sekhar Ija -
Two payment doc. for same Vendor in F110
Dear All,
In F110,the system is creating two payment documents for the same vendor with same payment method.
we have 3 open item(document) for this particular vendor,but the system is posting two payment document.
we have checked the Vendor master and FBZP payment method settings(Single payment is not selected in both),but how the system is posting two payment document for the 3 open invoice.
Do suggest.
Regards.Check the following fields in all the 3 invoices
They must be identical for 2 of them and different for 1
Paying company code
Sending company code
Account Number of Vendor or Creditor
Customer Number 1
Payee code
Currency Key
Payment Method
Short Key for a House Bank
ID for account details
Partner Bank Type
Business Area
Business Place
Indicator: Capital Goods Affected?
Grouping Field for Automatic Payments
Payment Method Supplement
Instruction key 1
Instruction key 2
Instruction key 3
Regards
Sach!n -
Hello to all of you,
Is it possible to put in the vendor masterdata that we pay all the bank charges when we do a payment to this vendor?
For example by the instruction key. Because I have seen that for several countries this is possible.
We have a vendor in Italy, but we have to pay all the bank charges.Hi,
I assume we are talking about a DME-file sent to the bank. When using formats derived from MT101, you can specify in a tag who will bear the charges.
Example: W1SE Corporate e-Banking CASH MANAGEMENT SWIFT,
Tag:
:71A: M Details of Charges
This field specifies which party will bear the applicable charges for the subsequent transfer of funds.
Usage rules:
One of the following codes must be used:
BEN: All transaction charges, including the charges of the financial institution servicing the ordering customeru2019s
account, for the subsequent credit transfer are to be borne by the beneficiary customer.
OUR: All transaction charges for the subsequent credit transfer are to be borne by the ordering customer.
SHA: All transaction charges other than the charges of the financial institution servicing the ordering customer
account are borne by the beneficiary customer.
There will be similar rules in place regarding the DME exchange you do with your bank.
Hope this helps,
Kind regards,
Rudolf
Maybe you are looking for
-
Hi, My requirement is as follows I have an equipment for which I need to have a Maintenance work for every 24hrs. My requirement is I have a production order to produce say 1000000 items. The machine capacity is 24 items in a day. (Machine produces 1
-
Mac App Store stuck on "Waiting to install"?
Whenever I try to update or install a new app from the App store, it downloads fine but then gets stuck at the "Waiting to install" stage. I have tried rebooting my system, quitting and reopening the App Store, quitting the App store and killing the
-
How come in Pages, i cannot drag and drop images?
how come in Pages, i cannot drag and drop images?
-
Actual Start Date vs Actual End Date - Activity
In an Activity, I would like to seperately enter the Actual Start Date and Actual End Date. - If I try this using (partial) confirmation, I receive a pop-up with an error that the two dates must be entered together or no dates can be entered. The ac
-
Adobe reader won't accept the password I know is right
So I can't download it. Help!