Incident Number INC000000175572

Problem Statement Submitted the order but received no confirmations

INC000000175511

The automated billing that should happen from the 33xx PO to 43xx did not generate. AR tried to do manual billing but got message: Tried to bill out and cannot process due system error

INC000000175114

The list is not getting displayed, with the SYSCO UPC appearing as Zero's, list qty as zero, original and current price not getting displayed

INC000000179763

An order just duplicated in the system. The order was transmitted via Express

INC000000167653

INC000000181170

order is placed at a certain time but didnt flow to SWMS till two hours later. That is the issue orders not pulling in a timely manner, when order was placed. Customers are arriving and will call and orders are not ready which are causing the customer to not get product Exception Message: Error from BAPI: ZRFC_SME049_ORDER_SUBMIT, Message text (ZQT Quote Number) is currently being processed (by uswe SVCOMX01)

INC000000181893

ST- A Redwood CPS job failed: Job 33587706 E1_D_SM_OM_SME059_DEF end in status KILLED-K in PE1,

INC000000147584

The freight seems to be high and pulling the incorrect values

INC000000183111

Customer 1*11347 is seeing Saturday as a delivery option HOWEVER they should not have this option and according to what we see in routing setup and their 3rd party ordering tool they should not be seeing this option.

INC000000183422

Error in editing list, Error from BAPI:ZRFC_MANAGE_LIST_V2 running in system, Message text: Sales document(List #) was not changed (List #) Failure executing function(com.sap.conn.jco.JCoException) when adding item from list to the order

INC000000351445

INC000000271238

Sales order is delivered and billed, and when looking at the qty in the ZSMR002 report, the shipped quantity of sales order is Zero

INC000000357763

Compass list 3*0406 is not showing under Customer 1*29241 in order management

INC000000348367

zsmr209 report and invoice print out do not appear to match

INC000000202911

Discount rule is not reflecting in OM for individual ship-tonumbers tied to sold-to numbers.

INC000000217582

Need old order guide to be copied to new order guide

INC000000219264

Orders that did not ship yesterday. They were on credit hold and released, but did not flow correctly to be processed.

INC000000220666

Defect- hand pricing is not allowed in OM-Express on DAS subs- it should be.

INC000000222115

Can you verify the order showing submitted is viable. Rep did not get confirmation.

INC000000229225

OM is sometimes forcing the price on an order to the recommended price regardless of MIN/MAX rules in ECC and the intended hand pricing adjustment of the OPCO.

INC000000147584

The freight seems to be high and pulling the incorrect values.

INC000000282672 INC000000277984 INC000000206464

Need to check why orders did not ship User is unable to open the the order guide in sysco market Customer is unable to print an order from Express. They are able to do so from OM Live so it is NOT a pdf issue and we have tried clearing the cache. The internet browser is IE8

INC000000201817

user cannot view items in the product catalog for an account in om express

INC000000269907

pricing will not load for order guide. Order will submit while pricing appears to be loading, and MAs will modify/reprice the order after submission and resubmit.

INC000000311700

Unable to access the ship to listed below in OM Express

Resolution Checked document flow in ECC , the order should be delivered and invoiced. Output ZSA0 is successfully triggered (Check the Partner field in the output type). The Partner listed in Partners function tab should match. Check table NAST to see if the output was successfully triggered. If there are further issues checj with CRM or HR team to make sure why the output was not sucessfully sent

Check from which intercompany PO the sales order is created.PR should be created from the SO during the Sales order sale. Check if any other PO is created on the same day against the PR. Make sure the delivery date on the original PO has not changed, if the delivery date is changed it will delete all the line items from the existing PR. For Incident INC000000171655 the sales order was complete when the PR was deleted which resulted in a completion which stated item requisition missing for material. Since the system did not find any PR, it added an incompletion to the sales order. Can ask the business to reject the line item with the incompletion and invoice can be created for the remaining line items or create a debit not for the customer The data being returned for the invalid items is coming from SAP. The products mentioned in the list are having SHIP_SPLIT indicator as blank,it should ideally have Y or N,blank does not denote anything,.EIM-MDM-SAPMaterial can take care of this. RFC - ZRFC_GET_LIST_DETAIL_V2

Since the first submit of the order happened at Time A and ended at Time B during which time the ZQT was also being modified (Time C), there would have been a record contention issue between the 2 operations (submit and modify) that could probably have resulted in an error in frontend. And because of this error , the user might have thought that the first submit did not create an order, so the order was re-submitted again at Time D. This caused the creation of 2 orders for the quote. Can check the transaction ZSMR049. The object name is ZRFC_SME070_CREATE_ZQT, ZRFC_SME070_MODIFY_ZQT, ZRFC_SME049_ORDER_SUBMIT Can check the VBAK table, there will be two orders referencing the same ZZ_QUOTATION. There is a duplicate order report ZSME285 to detect the duplicate orders and delete them. Check Will call cutoff time for the OPCO. For the incident the quote was created, however the order was was not submitted till 1.5 hours later, therefore the pickup time for the order was according to the time the order was submitted. According to the Will Call Cutoff time and pickup time, the time is populated in the shipping details for the arrival time, GI time, loading time, Material staging time and transportation planning time In the order submit history of OM EXPRESS: Log shows that the same quote is submitted twice by the user. The submit happened at time A and ended at time B. At time B, the user executed modifying the quote. Since they happened at the same time, record contention was encountered causing an exception to be thrown. The, after modifying, user submitted the quote again at time C. This created two orders for the same quote. This issue is off duplicate order issue va OMX.Charm 2000006121 has been created to rectify the issue. Assign to Redwood CPS Scheduling team for analysis.

Gross Weight is calculated as Quantity multiply with Gross weight Per LB of the material,Net Weight is calculated as Quantity multiplied with Net Weight Per LB of the material . The entries are updated in the VBAP table for the gross weight and Net weight and and accordingly the value of Freight condition Typis determined. Change in value of Gross Weight changes the value of ACOGS changes in Condition Tab of that line Item. Change in the value of ACOGS is shown in the change history of the document. Example SO1001803970 , net weight of the material in material master is 19.9 LB, quantity of the material in SO is 18, so actual weight determined should be 19.9 *18 = 358.2 , but instead the weight was again multiplied with qty and the determined weight was 358.2 * 18 = 6447.6.checked the change log in both the SOs and were not able to find any changes done to the order quantity or to the net weight manually resulting in wrong net weight , ACOGS and freight calculation. There was no resolution to the ticket as issue could not be replicated

In the OM Express screen, Highligted dates show as offdays. Placing cursor on Saturday and Sunday show it as a offday. Internal users(MA) would be able to place orders all days of the week irrespective of working days maintained in ECC. Offdays would be grayed out only for customers. Customer was a B2B customer and all orders were places from B2B, it seemed the customer was not passing the RDD(DTM)[Segment E1EDK03 002] field in EDI 850[Basic type: Orders05, Message type: Orders] for some of the orders because of which the RDD gets defaulted to the next day which is standard SAP.
Tried replicating the issue. Item is deleted from list successfully and list is saved. Since the issue could not be replicated, the user continued using the duplicate list created.

The exception (104) RFC_ERROR_SYSTEM_FAILURE raised from sap package (com.sap.conn.jco.JCoException), its a SAP issue. This exception will display while running RFC - ZRFC_SME020_REASSIGN_LIST. PFB the input field for the RFC: I_INQUIRY : I_USER_TYPE : I_ACCESS_TYPE : OWNER_NAME SHIPTO : SOLDTO : In transaction SE37 can analyze FM ZRFC_SME020_REASSIGN LIST, The issue was caused by both a bug in ZRFC_SME020_REASSIGN_LIST and also by the kind of name assigned to the list.The code could not correctly When running the report with the following parameters: SD document Catalogue, document number, RDD, Soldto-party, and the reporting level is Schedule line. The shipped quantity column is displayed with 0 qty. The shipped qty is from the internal table 'gt_shline' of the field 'Ifimg', it gets the data from table 'lips' and 'likp'. When the field 'WBSTA' is 'C', no qty amount is populated. 'WBSTA' is from the table 'VBUP', its the goods movement status. The WBSTA value is blank fro the VBELN value, however for the outbound delivery the value of WBSTA in table VBUP is C. The goods movement status in the outbound delivery is complete. As tested in other enviroments, the report is behaving in a similar way and the shipped qty is appearing as zero The reason for this was the Customer 1*29241 is maintained in ECC as ship-to-party and not a sold-toparty(check partner functions tab in the sales area data). Shared ZBIDs 3*51897 is shared only for sold-to-parties attached to a higher level group customer which is 3*406. Can check in table KNVP, the customer 3*406 will be linked to 1*2924, and the partner function will be ZL
As per analysis the ZSMR209 report is displaying correct line items. Checked the VBAP table, POItem column (Z001: indicates a swap, MAN- manual substitution), the line item rejected with rejection reason 71 will not be displayed in the report. Can check in table VBRP which materials are part of the invoice (billing document)

It appears that the entire discount rule for Torchys Tacos is not reflecting in OM for individual ship-to-numbers tied to soldto-numbers despite being correctly set up in ECC. RFC: ZRFC_SME038_PDPE_WRAPPER, Input: I_SOLDTO, I_SHIPTO,I_PRICING_DATE, I_USERTYPE, IT_PRODUCTS-PRODUCTS_ID, OUTPUT: ET_PDPE_PRICE-PRICE:"caseOriginalPrice", CaseOriginal Price+ caseSalesAssciatedAdjustmen will be displayed as the current price of item on OMLIVE page. caseOriginalPrice and caseSalesAssociateAdjustmen are retrieved by RFC ZRFC_SME038_PDPE_WRAPPER, caseSalesAssociateAdjustment: returned by key- OUT_ET_EXTEND_PRICE_SA_ADJUST_KEY="SA_ADJUST", CaseOriginalPrice: returned by key-OUT_ET_BASE_PRICE_PRICE_KEY="PRICE",The return 'PRICE' is '72.12' and the 'SA_ADJUST' is '0.00', its different then the price displayed which is '71.23', RFC returning price which matches the ECC order price. There is different price for a particular item on different delivery days. There is one RFC to retrieve price before submitting order and another RFC to retrieve price after submitting order. Before submitting order: Product detail information (including price) is retrieved by RFC - "ZRFC_SME038_PDPE_WRAPPER". However, price returned for different delivery days by the RFC are same. Checked with ABAPer, the price is returned by standard function /SYPDPE/NET_PRICE_API. This standard function always return same price value. ABAPer guess this is the root cause. While Submitting order: Product detail information in (including price) is retrieved by RFC - " ZRFC_SME065_VIEW_SO" again. Way in which items are sorted and sequenced Express is different from Live.

Sequencing in Express is based on Category even when you select the Do not Group option.(if items are categorized in the list)Please find below the steps to sequence the items in the list: 1. Open the list and click on Edit List button on the top of the list grid 2. On the left navigation window, My Categories section will be shown. 3. Click on Uncategorized or any other custom categories which you have created. 4. Now in the list grid, you will be able to change the sequence number in the column with header #. 5. Or, you can drag the row of the line item and rearrange it. 6. Then click Save List button. Sequence changes will be saved. Checked the sales order, if the schedule lines are confirmed, there are no incompletions on the order, credit block released before DDL. If all these parameters are satisfied, the orders should be picked up by DDL for delivery document creation. Can also check the change logs in ZSME013. Can route incident to warehouse team to check if the DDL times have been changed on that day. Warehouse team confirm on the As checked from front end, for the DAS items, it only check quantity change but not check price change. If the quantity of a DAS items is changed, it means the order is changed/updated. If the price of a DAS item is changed, it does not mean the order is changed/updated. So the error message "There is no change to submit this order." returns. In order to check if there is an issue in ECC, simulate an order through ZVA01 in ECC, if the ZH00 is editable(hand-pricing is active), give a positive and negative manual adjustment to see if the price changes. Make sure to save the changes to ensure if the sales document is getting saved. The hand pricing prerequisites are: The ZHR1 record should be maintained for the plant, the customer is assigned as a TRS account type in the customer master, min and max values should be defined also. As per our analysis on OM Express and backend (ECC) the hand priced value for the DAS subsitute item should be displayed Check the email address in the general data of the customer master, if no data is maintained then the e-mail address field is not maintained. In the Sales order in the partner tab, the ER territory sales is maintained so they will receive an email confirmation, in PC1, (Display person), put the business partner ID to determine if email ID is maintained for territory sales/MA.

OM EXPRESS creates manual adjustment which goes significantly below the MIN/MAX rules. Based on the parameter "BACKWARD_COMPATIBILITY_MODE", the RFC - ZRFC_SME038_PDPE_WRAPPER or ZRFC_PRICING_V3 will be called to retrieve currentPrice, caseUpperLimitPrice and caseLowerLimitPrice.Input parameter of the RFC: fetchPricingList: is a list of ProductUniqueDataKey, customerShipTo: the ship to account id of the logged in user, customerSoldTo: the sold to account id of the logged in user.userIntExtType: the internal or external user type,Output value:CurrentPrice : PRICE CaseUpperLimitPrice: UPPER_PRICE, CaseLowerLimitPrice: LOWER_PRICE,PFB the expression to calculate the margin price.RecommendMargin = price(CaseUpperLimitPrice-CaseLowerLimitPrice).The returned value CurrentPrice, CaseUpperLimitPrice and CaseLowerLimitPrice are stored in cache. These value will be refreshed in a period. CurrentPrice, CaseUpperLimitPrice and CaseLowerLimitPrice may change after refreshing in a period. So RecommendMargin may change timely. The front-end team check: PFA the MAX price (77.18) and MIN price (36.58) for item# 9190430. As the user recall, he did not change the price to 26.55 while creating order. However, the price for the item is set to 26.55 when user open the submitted order. When user tried to markdown the price from 39.00 in OMExpress, he can only markdown to 36.58 (it's the min price). But he could not markdown the price lower than the MIN price. So the price send from front end is correct. The Back-end team checked the ZADJ condition type is being applied which is bringing down the price of item below Min which is affected the gross profit. Check the condition when this condition type is applied during submission of the order. The Appdev team runs the function ZRFC_SME038_PDPE_WRAPPER with a material and customer. The price of the material is #, but there is a MA Manual Adjust ($)(ZH00) which affects the last price(ZCLP). The MA manual adjust is by the function PRICING, and the manual Adjust= <FS_KOMP>-ZZKZWI1_SUPR(51.45) - <FS_KOMP>-ZZKZWI12_SUPR(39). Under condition ZCPF, there is price-base from table KONV, the ZZKZWI1_SUPR is the base price. And ZZKZWI12_SUPR is the last price, its calculated in accordance with the corresponding calculation rules out depending on the data in KONV. Simulate orders in ECC to determine if able to hand-price the material below the MIN price. Check the prerequisites of the LP/LM (Last price/Last Margin) activation. The customer should be a TRS customer, account type should be TRS, check the condition types ZXCC is active for customer and material. LP/LM is active for customers/material combination and customer will be charged according to the MA rule in the ZXCC records, exclusive of hand-pricing (If the ZXCC records have MA rule as 3, which means higher of LP and LM will be considered. In the order if ZCLP is higher then ZCLM, ZCLP will be picked. Ideally the customer

Do the simulations of the following scenarios to determine the root cause of the issue:Scenario 1 :- Simulation of Sales Order in Production.Scenario 2: Checking the Sales Order of The Invoice mentioned in the Incident having the Material at the item levelScenario -3 Taking other material of same PO and try simulating an order again Scenario -4:-Replicate the Scenario in DE2 Serve,rGeneral Information:Opening the material in MM03, in the basic data 1 tab is the gross weight and net weight. Check in the purchase order in the quantities/weights tab what is the net weight and gross weight .Create an order in ECC and check for the freight conditions which are ZF03 and ZF05. Check in the shipping tab of the sales order the net weight and gross weight. Value of VF03 = gross weight per 1000LB* freight value per 1000 LB. Value of ZF05 will be gross weight per 1000LB * freight value per 1000 LB.After checking the sales order of the invoice mentioned in the incident , the gross value is very high in the shipping tab of the document, therefore freight is getting calculated on the value of the gross weight. Check the Cond.base value which picks up the value of the gross weight in the shipping tab of the sales order rather than picking up the gross weight from the material and multiplying it by the total quantity. Simulate an order with another material of the PO, the value of the freight should depend on the gross weight. Value of ZF03 condition type will be Gross weight per 1000 LB * freight value per 1000 LB.Simulate an order with a non- catch weight material. In the shipping tab, value of gross weight = value from material master * quantity ordered. Value of ZF03 condition type = gross weight per 1000 LB * freight value per 1000LB. Try changing the gross weight in the sales order manually, the value of the freight in the condition tab depends on the gross weight of the material in the shipping tab of the sale order. The value of the condition ZF03 is re-determined. It can be seen that the changes in the gross weight is not captured in production log. However when the gross weight changes, the value of ACOGS changes also which is captured in the production log. So when ZF03 changes, ZC50 also changes. It was determined that the user did not change the ACOGS as they do not have authorization, however they did change the reason for rejection to blank. The issue was replicated in the dev environment and Check if the orders are present in ZTSC_ROUTE_SWMS table, if so sent to COE-Warehouse team to analyze This is an cache issue , clearing the cache will resolve the issue. User needs to press F12 and clear cache This ticket belongs to the front-end team, the user should have a up-to-date Adobe reader.Check the settings in the adobe reader and the Internet Explorer settings that Adobe Reader is enabled as a plugin

1. Check in OMEXPRESS, no categories are loading for the account. Appdev team determined the parameters based on which the categories are decided for the account. RFC-ZRFC_PROD_STOREFRONT is called to retrieve the product catalog. Input parameters: shipTo: represents a customer ship-to account to whom we ship the goods, standardType: denotes the type of standard to retrieve. C for CMIM data and G for GS1 data. Executing the RFC mentioned ZRFC_PROD_STOREFRONT for CMIM C and GS1 G, Customer ########, Output. Table ET_RETURN. Table ET_CAT is empty. RFC ZRFC_PROD_PRODUCT calls FORM GET_DATA. RFC ZRFC_PROD_PRODUCT calls FORM GET_DATA. In the FORM GET_DATA, the ET_RETURN table gets filled with the message. Ticket assigned to CRM team to get catalogue set up for customer

Assign to Appdev team to check if rfc is loading price values, or is it taking time to load into the front end. As debugged from font end, the cost of product ###3 jumped from ##3to ##after submitting order. In open order (before submitting), product cost is returned by RFC - ZRFC_SME038_PDPE_WRAPPER, PFB the returned costcombase. Combase is from field ZZKZWI8_SUPR which is in the VBAP table. In submitted order (after submitting), product cost is returned by RFC - ZRFC_SME065_VIEW_SO, cost is returned by key ZTSD_PRICE. The GP value is calculated based on product price, product cost and order quantity. As the cost is changed, so GP value is changed two. Execute three scenarios: Scenario A: RFC : BAPI_FUNCTION_NAME = "ZRFC_SME038_PDPE_WRAPPER", Shipto, Date, Price, Combase. Price and Combase is returned. The price is from function /SYPDPE/NET_PRICE_API, price value is in field NET1B and the cost value is in field COMBASE. Scenario B: RFC: BAPI_FUNCTION_NAME = "ZRFC_SME070_VIEW_QT" will be called, and get price from result with OUT_ET_ITEM_ZTSD_PRICE_TABLE_KEY = "ZTSD_PRICE";openOrderNumber, combase, OriginalPrice = ORIGINAL_PRICE, the function gets the data from table vbap, field ZZKZWI8_SUPR and ZZKZWI12_SUPR. Scenario C: RFC : BAPI_FUNCTION_NAME = "ZRFC_SME065_VIEW_SO" will be called , and get price from result with OUT_ET_ITEM_ZTSD_PRICE_TABLE_KEY = "ZTSD_PRICE", Order #, combase= Gross_PROFIT, OriginalPrice: Original_PRICE. This function is get data from table vbap, the field ZZKZWI8_SUPR and ZZKZWI12_SUPR. This Check the user can access account or not. If not ticket belongs to the CRM team. Territories are returned by RFC - ZRFC_SME021_PERMISSIONS_ACCTS.Input: IN_I_APPLICATION_ID: 02IN_I_USERID_KEY: DMAR5301.Output:TE_RETURN.TE_SHIP_SOLD. Check the return data for the territory mentioned in the ticket. Territories are returned by RFC -- ZRFC_SME021_PERMISSIONS_ACCTS. Input:IN_I_APPLICATION_ID: 02,IN_I_USERID_KEY: DMAR5301.Output:TE_RETURN,TE_SHIP_SOLD---->TERR_ID(T10502277).TE_TERR_ID. Checked and the setup looks good in the backend