ROSS: New Product Intro; Part Requirements to Order

Created by Kathy Kale, Modified on Thu, 24 Apr at 9:38 AM by Kathy Kale

New Product Introduction changes


When you are ready to introduce the product:

  • In Blocking – Product Base blocking
    • End date the Intro blocking.  Without this change, ALL the product sizes cannot be added to orders.
    • Make sure any state or country blocking is current.
    • Product Size blocking should be added for any product sizes that were setup but are not being introduced.
  • In SCC Prod Base Maint.:
    • Correct this data:
      • The long name is the price book name.
      • Change the intro date here
      • Change from JSNYET to JS
        • “PrBk Can” changed to “Y” if this is on their price book.  Only mark the “C” part codes if they are created.
      • Make sure the price book description is filled out
      • Make sure the price book sort is filled out and not “1” which we use until Cali lets us know where to put it in the Product Group.
    • In the SCC Product Term/Avail:
      • Correct this data:
        • Change “Prod Class” from JS UN to JS           unpublished to published
        • Change “Price Book” from JSNYET to JS on each product size
        • Change to “Ord Y/N” to “Y”  allowed to order.
        • Activate the Product Master  “Sts Flg” = “I” inactive to “A” active
        • Activate the Product Warehouse
        • Make sure the weight is filled in 
          • Without this, the order weights will be wrong.
      • On the SCC Price List
        • Verify the price matches the price book
          • Dsc Y/N   - if the weight breaks are not happening, correct this field
          • Pricing ProdGroup – if the quantity breaks are not calculated correct this field:
            • NODISC
            • 55-55
            • RTU,RESTRM,AEROSO,FOAMIQ,URINAL,XPRESS
            • Canadian products need the correct Pricing Product Group as well as the Discount Y filled in!!!

 

 

  • In SCC Product Term/Avail 
    • The PrcBk SizKey indicates the size description on the price books
      • If it is marked on a price book (even JSNYET) this is required.
      • You will see the “Container Desc.” with the text that goes with that size key.
    • You should also make sure the “Category Code” is filled in.

 

 

Please do not include the “, 275*Tote” in the description of the product.   It is a carry over from many years ago.  It is not necessary any more.

 


Part Requirements for ordering / Terminating


Sales orders flag is the first thing to mark a product for ordering or not ordering.

It is one of many things that are necessary to be able to order a part.

 

To be able to order a part:

  • PRODUCT REQUIREMENTS:
    • It has to be marked as sales orders flag = “Y"
    • It has to have no blocking
      • Discontinuation blocking (at the product/size level)
      • Intro blocking  (at the base level)
      • No restriction for the customer ordering (state or country blocking)
    • It has to have active pricing with the order date between the start and end dates of the price
    • It has to have activated PRODUCT_MASTER and PRODUCT_WAREHOUSE activation status
      • These fields are meaningless.  Anyone who exits a part/warehouse in a wrong way can deactivate a part.
      • We have a job running regularly to activate products.
      • We have a job running regularly to activate product warehouses.    
  • CUSTOMER REQUIREMENTS:
    • It has to be marked as sales orders flag = “Y"
      • some non-ordering customers are marked as sales orders flag = “N" 
        • corporate office locations
        • stock transfer locations (some are real physical locations, some are "RM" assigned only)
    • it has to have a price code added with a valid price for the product being ordered
      • Customer Price Codes to add price codes
    • It has to have activated CUSTOMERS and CUSTOMER_ADDRESSES activation status
      • These fields are meaningless.  Anyone who exits customer/address in a wrong way can deactivate them
      • We have a job running regularly to activate customers that are allowed to order.
      • We have a job running regularly to activate customer addresses without [TERM] in the name.
    •  SALES_ORDER_TYPE
      • this will determine what kind of order will be processed (it does not prevent orders from being added)
        • STOCK
        • FOREIG
        • TRANS
        • CC
        • EUORD


Requirements for part termination: 

  • The product termination process starts with setting sales orders flag = “N”
    • when sales orders flag = “N”,other fields are automatically changed to match:
      • Product Class is set to JS UN or PM UN
      • price book is cleared
      • Canadian price book is cleared
      • when the termination date is keyed, the status is flipped to "T"
      • the activation status is changed when the part is terminated. 
  • [TERM] on the name of the product is just a way to know the intent is to terminate it.
  • Termination date must be filled with a date (not 01-01-2100)  
    • this field does NOT stop the order from happening.  
    • It is a notation for documentation to know the date when the termination happened.
  • Use SCC Product Term/Avail ross option
    • change the above 3 fields F5
    • menu option:  Terminate Product 
    • change 2 description to [TERM]...
    • Eff Off date change to today  
    • Termination date will pull in from the prior screen where it is a requirement.
    • Update "Yes"


  • Use SCC Part Blocking to add blocking
    • Insert key to add new blocking.  it will fill in the text as you key the suggested part
      • if the product base matches the blocking part,
        • it will add to the blocking message "in another pack size" 
        • if not the same base, it will just suggest that product
          • it is up to the order entry person to suggest the appropriate size



Requirements for customer termination: 

  • use program:  SCC Customer Maint, Stmt Acct
  • FIRST terminate each address
    • [TERM] added to each name        F5
    • Menu option:
      • this will deactivate the address
      • the activation status and [TERM] on the name are the ONLY flags at the address level!!!
      • PRICE_CODE on the address records are NOT USED any more
  • [TERM] on the name of the customer
    • all the addresses need to have [TERM] in the name in order to be able to terminate the customer
    • Menu option:
    • Customer Price codes - NO changes are currently being made to the price codes assigned for customer
    • Termination date must be filled with a date (not 01-01-2100) 
      • this field does NOT stop the order from happening.  
      • It is a notation for documentation to know the date when the termination happened
      • When it is successfully terminated, you will get this message:





BLOCKING NOTES:


Initially show basic fields

show a menu after to see:   

1.  Blocking active

2.  Blocking all   (including terminated)

3.  Pricing information


Three main selections:

1.  select ALL parts for a Country blocking - key the country and see the blocking

2.  select ALL parts for a State blocking  - key the state and see the blocking

Get the data from table:   scc_order_blocking


Show product base first, then show the Part code blocking



3.  select a product base and see all the blocking for the base   PRODUCT_MASTER(SCC_PROD_BASE)

       1.  Y/N if Introduced yet and introduction date   SCC_INTRODUCED_FLAG & SCC_INTRODUCTION_DATE

       2.  STATUS &  SCC_TERMINATION_DATE

       3. description    SCC_PROD_BASE_NAME_125

       4. SCC_PRICE_BOOK & SCC_PRICE_BOOK_SORT  &  SCC_PRICE_BOOK_DESCRIPTION

      5. SF_BRAND

      6. SCC_PRIMARY_CATEGORY

       


2.  show sizes for this PRODUCT_MASTER(SCC_PROD_BASE)


  1. Size                               PRODUCT_MASTER(SCC_SIZE_KEY)     SCC_SIZE_MASTER(SCC_SIZE_NUMBER_2)    
    1. Part Code =SCC_PROD_BASE  +  SCC_SIZE_NUMBER_2 
  2. TERMINATED                PRODUCT_MASTER( SCC_TERMINATION_DATE)
  3. Allowed to order          PRODUCT_MASTER(SALES_ORDERS_FLAG) = "Y" or "N"
  4. Activated                      PRODUCT_MASTER(ACTIVATION_STATUS)  
  5. show the Intro blocking ( new part codes )  release date for intro.
    1. SCC_ORDER_BLOCKING(SCC_PROD_BASE)
    2. SCC_ORDER_BLOCKING(PART_CODE)
    3. SCC_ORDER_BLOCKING(SYS_COUNTRY)
    4. SCC_ORDER_BLOCKING(SYS_STATE)
    5. SCC_ORDER_BLOCKING(TEXT_MESSAGE)
    6. SCC_ORDER_BLOCKING(ACTIVATE_DATE)
    7. SCC_ORDER_BLOCKING(DEACTIVATE_DATE)
  6. show the Discontinued blocking (terminated part codes  or never introduced) starting and ending date for discontinued.
  7.  setup in the warehouse and activated warehouse  PRODUCT_MASTER(SCC_WMS_WAREHOUSE)
    1. FG
    2. EU
  8. Show as a separate window:  Pricing
    1. Marked in Price book   PRODUCT_MASTER(SCC_PRICE_BOOK) = JS or JSIPG
    2. Is pricing setup - we will decide if we want to show the pricing.  check for "D" price code
      1. SOP_PRICES(COMPANY_CODE) = "1"
      2. SOP_PRICES(PRICE_TYPE) = "4"
      3. SOP_PRICES(DIVISION) = "00"
      4. SOP_PRICES(WAREHOUSE) = "FG"   PRODUCT_MASTER(SCC_WMS_WAREHOUSE)
      5. SOP_PRICES(PART_CODE)
      6. SOP_PRICES(PRICE_CODE) = "D"  distributor prices
      7. SOP_PRICES(VALID_FROM_DATE)
      8. SOP_PRICES(VALID_TO_DATE)
      9. SOP_PRICES(SALES_PRICE)
    3. discount allowed.                             PRODUCT_MASTER(SCC_DISCOUNTABLE_FLAG)
    4. product weight                                PRODUCT_MASTER(WEIGHT_GROSS)  &                                                                                                                          SCC_WMS_ST_ITEMS(SCC_ACTUAL_WEIGHT)  &                                ,.SCC_WMS_ST_ITEMS(UNIT_OF_MEASURE) <> '"PL" for pallet weight
    5. product weight discounts   
    6. product quantity level discounts    PRODUCT_MASTER(SCC_PRICING_PRODUCT_GROUP)

     


2. show as a separate window:  any restriction blocking. 

            1. by state

           2. by country

           3. any overrides to the blocking.

           4. blocking messages


Toggle to show all terminated blocking as well.





Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article