Eric Lehti
VIP Member
How do you teach your users to not set up additional(duplicate) JDE Address Book records for the same entity, if it is a customer AND a supplier?
Do you use the F0101 field ABAT1 to designate an entity as Vendor/Supplier/Customer/Employee/whatever?
I just learned this morning that our people set up multiple Address Book records for the same entity if it is both a customer and a supplier.
Example: We already have a customer set up with an F0101 Address Book record and an F0301 customer record. F0101 Search Type field ABAT1 is 'C'. People in Sales and Accts Receivable always do Name Search (P01200) with ABAT1 set to 'C'.
If our Accts Payable people want to purchase from this same entity, they perform name search (P01200) on ABAT1=V'endor. On not finding this entity in Address book (because they searched on ABAT1=V, they create a new F0101 Address book record with ABAT1=V and set up a F0401 Vendor master record.
User express surprise that a single JDE Address book entry can be used for all purposes (Accounts Payable, Accounts Receivable, Human Resources.
Do you use the F0101 field ABAT1 to designate an entity as Vendor/Supplier/Customer/Employee/whatever?
I just learned this morning that our people set up multiple Address Book records for the same entity if it is both a customer and a supplier.
Example: We already have a customer set up with an F0101 Address Book record and an F0301 customer record. F0101 Search Type field ABAT1 is 'C'. People in Sales and Accts Receivable always do Name Search (P01200) with ABAT1 set to 'C'.
If our Accts Payable people want to purchase from this same entity, they perform name search (P01200) on ABAT1=V'endor. On not finding this entity in Address book (because they searched on ABAT1=V, they create a new F0101 Address book record with ABAT1=V and set up a F0401 Vendor master record.
User express surprise that a single JDE Address book entry can be used for all purposes (Accounts Payable, Accounts Receivable, Human Resources.