Procedure for creating/changing intercompany customer & vendor master records.

1. Receive support message ticket indicating which unit code is requested.

 If create/change is triggered from accounting document, create the
ticket ourselves using group 1713 (Ent – Consolidations & Fin.
Planning) as the sold-to group.

2. Obtain unit code name & address information from Unit Code Database (via
Account Flex). If support message included name & address information,
confirm that request agrees with Unit Code Database. If not in agreement,
respond to requestor that SAP will need to agree to Unit Code Database and
have them follow up with business partners and Unit Code Database. Rod
Parrish & Chris Houtakker are Unit Code Database administrators.
Link to unit code database:
http://accountflex.deere.com/AcctFlexMaint/servlet/com.deere.u90.ac
countmaintenance.view.servlets.UnitSearchServlet

3. Once any differences are resolved, check transaction OX15 (Trading Partners
/ Define Company, Table T880). If the unit is not already included in this
table, we’ll need to configure the value with the naming convention uu0000
and send ZREQs to the division transport managers. We’ll want the transport
for the requesting division and the JD transport moved to the P client as
quickly as possible. The other divisions can follow their normal transport
process; the only negative impact of not moving it faster is that the IDOC
from PJD to that division P system will fail. This is not normally an issue.

4. Notify Reporting team of new trading partner for update of T-3 exhibit.

After any needed Divisional and JD transports for Trading Partner have moved to
"P" clients, use XD01(Create Customer) and XK01(Create Vendor) to create the
intercompany customer and vendor. (You will not be able to create any Customers
or Vendors until you have been added to the I/C cust auth table ZVSVCUST_AUTH
with I/C cust auth group = Z130 , and to the I/C vend auth table ZMSVVEND_AUTH with
I/C vend auth group = Z010). The associated maintenance trans for these tables are
ZV_CUST_AUTH and ZMSVVEND_AUTH.

5.
 Account Group field:
 For Customers, use account group Z130(Company w/ ext bill &
# assign);
  For Vendors, use account group Z010(Inter-company Vendor);

 The account number naming convention is 99999XYY00, where "X" (in

position 6) = an alpha character denoting the account type, and "YY"
= 2 byte unit code. The value in position six, is a P (Plant/Factory), S
(Sales), or C (Corporate or Credit) depending on the Unit Class and
Unit Identifier Code from the Unit Code Database. In general,
manufacturing facilities have a unit code beginning with a letter. The
Legacy Unit section on the Maintain Unit Information screen of the
Account Flex/Unit Code database website
(http://gotodealer.deere.com/AcctFlexMaint/servlet/com.deere.u90.ac
countmaintenance.view.servlets.UnitSearchServlet) can be used to
determine which letter is appropriate.

 The name of the intercompany partner should be the Legal Name from
the unit code database; but, there are cases where we would use a
phrase such as John Deere Waterloo Works, a Division of Deere &
Company to provide more specific identification when there are
multiple operating units within the legal entity.

 Enter address from Trading Partner. Duplicate accounts may be

encountered using the same address. These will need to be reviewed
on a case by case basis to determine the appropriate course of action
to take. Use www.geotax.com to resolve multiple District/County
issues if encountered. Address details can also be found on the
AcctFlex/Unit Code database; but, the region is generally not included
for many countries. Use Google or Wikipedia to identify the region to
be used for a specific city.

 enter phone number for account (from the Communication screen of

AcctFlex)

 (if applicable) enter legacy customer or vendor number in the Data

Line (ADDR1_DATA-EXTENSION1) field

 On the Control Data tab, enter the appropriate Trading Partner value.

 Also, if creating a new I/C account that is for the same unit as an
existing one, but with a different value in byte 6, like a "T", then copy
over the VAT and Credit Information numbers to the appropriate field
on the new account, if they are populated on the existing I/C account.
However, this does NOT apply for Brazil, where all of these numbers
 must be unique; there is code on PJD that will prevent the account
from saving if this is attempted for a Brazil unit.

 VAT numbers may be required for Non-US units, and can be

determined via Account-Flex or via Business Sponsor. Tables KNA1(for
Customers) and LFA1(for Vendors) can be used to determine if VAT
numbers are being used for a given country.

 Similarly, if the new account is for a European unit, then the

corresponding vendor and customer number will need to populated on
the Control Data tab after both have been initially created. The
system will not permit the entry of the corresponding account until it
has been created and saved, so you may need to go back into each
account in edit mode and add this after the fact.

 Save changes when done, and this will send new accounts (via ALE) to
all production "P" boxes in the enterprise:
i. Customer IDOC info:
1. Basic Message Type = DEBMAS06
2. Logical Message Type = ZVSV_CUSTOMER
3. Sending Partner Number = PJD410ALE
4. Sending Partner Type = LS
ii. Vendor IDOC info:
1. Basic Message Type = CREMAS04
2. Logical Message Type = ZCREMAS (GLOBAL VENDOR DATA)
3. Sending Partner Number = PJD410ALE
4. Sending Partner Type = LS

6. Once created, the customer and vendor will automatically ALE to the
divisional "P" Clients. As mentioned in point 3, the IDOCs will fail in the
divisional clients until the trading partner transport has been moved. Please
note: if ALE does not generate IDOC, then it can manually be sent via BD12
(Send Customer) or BD14 (Send Vendor) by specifying the acct number,
logical message type, and receiving partner number. (Please note: if the new
I/C account data is needed on lower clients, it will have to be manually
recreated on the target client, or BD12/BD14 can be used to manually push it
from the corresponding JD client(CJD/QJD) to the target "C" or "Q" boxes.
The data from PJD is supposed to automatically push to QJD and CJD.)

7. Update Sharepoint Documents that list all intercompany customers and

vendors:
 Customers file (data source KNA1 table):
http://share.deere.com/teams/FICO_Projects/FICO%20Documentation
/IntercompanyCustomers.xlsx

 Vendors file (data source LFA1 table):

http://share.deere.com/teams/FICO_Projects/FICO%20Documentation
/IntercompanyVendors.xlsx