SalesPerson and Sales Territory details - Customer Card and Customer Address Maintenance

In a previous post, an interesting case related to populating sales person and sales territory details when creating a new sales transaction entry sheds a light on an integration issue that is highly dependent on sales person and territory setup. In this essence, I believe it would be quite important to provide further valuable information as related to the same topic. 

In the sales module, there are two specific windows to be considered when filling out the sales person and territory assignment with a specific customer, which are: Customer Maintenance Window and Customer Address Maintenance window. Technically speaking, the data is stored in RM00101 (corresponding to the customer card) and RM00102 (corresponding to the customer address maintenance). 

Database Tables:

• RM00101 - Customer Card (Cards > Sales > Customer)
• RM00102 - Customer Address  (Cards > Sales > Customer Address)

Here are some facts:

• When filling out the sales person and territory ID in the Customer Maintenance window, the corresponding customer address details are updated accordingly.
• When filling out the sales person and territory ID in the Customer Address Maintenance window, the customer card is NOT updated accordingly.
• When creating a new sales transaction (SOP document), sales person and territory details for a specific customer are derived from the Customer Address Maintenance window (not the customer card)
• In case the both customer maintenance and customer address are filled with sales person and territory details, then the data stored in "Customer Address Maintenance"  will default when creating a sales order. Meanwhile, if there is no details in Customer Address window, the details will be derived from customer maintenance window.

Sales Person and Territory Details - Setup and Default Values

Therefore, when validating sales person and sales territory details. Checking the customer card, customers smart list or customer master report doesn't mean that the "Sales Person" and "Sales Territory" details are the ones that will be populated as default values when creating a sales order. The correct place to check is your customer address (RM00102)

The following SQL Statement will help you reconcile your sales person details between customer maintenance window and customer address window (RM00101 versus RM00102)

     

SELECT  A.CUSTNMBR ,

        A.ADRSCODE ,

        A.SLPRSNID Master_SalesPerson ,

        A.SALSTERR Master_SalesTerritory ,

        B.SLPRSNID Address_SalesPerson ,

        B.SALSTERR Address_SalesTerritory

FROM    dbo.RM00101 AS A

        LEFT OUTER JOIN dbo.RM00102 AS B ON A.CUSTNMBR = B.CUSTNMBR

                                            AND A.ADRSCODE = B.ADRSCODE

WHERE   RTRIM(LTRIM(A.SLPRSNID)) <> RTRIM(LTRIM(B.SLPRSNID))

        OR RTRIM(LTRIM(A.SALSTERR)) <> RTRIM(LTRIM(B.SALSTERR))

               

Best Regards, 

Mahmoud M. AlSaadi

Rule of Thumb | Megring Line items when Migrating a Requisition into a Purchase Order

There is one important missing piece related to the requisition management in Dynamics GP that is left unexplained or not quite common for users working with the new requisition cycle. It is specifically related to migrating the existing fully approved requisition into a purchase order. 

Requisition with two line items (almost identical)

The scenario that is proposed implies that the line items have the following identical parameters or characteristics which are:

• The two line items have the same item number
• The two line items have the same vendor
• The two line items have the same unit cost

In case the conditions above are true, the system will automatically merge these two line items under one line item and purchase order when purchasing the requisition or migrating this requisition into a purchase order. Let's see how line items will be grouped by and redesigned on the purchase order preview window:

Purchase Order Preview Window

As shown above, the original requisition has the following line item:

1. Item Number (Paper) , Item Description (Paper A4), Unit Cost (1) and Vendor is (Acetrave0001) , quantity is 10
2. Item Number (Paper) , Item Description (Paper A3), Unit Cost (1) and Vendor is (Acetrave0001), quantity is 20

On the other hand, the generated purchase order is redesigned to include one line item which is:

1.  Item Number (Paper) , Item Description (Paper A3), Unit Cost (1) and Vendor is (Acetrave0001), quantity is 30 (which is the sum of both line items above)
   

Although, the important note to keep into your consideration that this is the default behavior but still it is not obligatory as you can still manipulate the line items which will be created in the desired purchase order. This can simply done through the "Organize" button on the left navigation pane, through which you can separate the line item in another purchase order and; as a result, keep the separate two line items in separate purchase orders. 

Organize Purchase Order Preview

Follow the steps below:

• First of all, click on the button prior to the organize, which is add vendor. To add a new Purchase Order, for which you should first fill in the vendor ID field.
• Then, click on the Organize Button highlighted above, and a warning message will pop up stating the following "please select a source node followed by a destination node"
• Click on the required node from the two above, and then click on the new node created which is the destination. 
• This will create two purchase orders including separately your original two line items, without having them merged under one purchase order and one line item. 

Line items are separated into two purchase orders

Best Regards,
Mahmoud M. AlSaadi