-
Configuration
- 7640 - Cannot Run Exchange Rate Revaluation for Sep and Oct
- 7986 - To Create New Distribution Channel for MAI Company_1
- 7994 - Add Column in Customer Statement PDF Form_All Company
- 7655 - To assign 1000 company code
- 7670 - To create new storage locations for Wisarra (1210), MAI (1410)
- 7705 - To Create 2 New COA
- 7770 - Millco New Storage Location
- 7907 - To create new distribution channel & assign to 16SO
- 7917 - It appears as due ahead of the due date
- 7978 - Consignment Issue CCIS Type Not Blocked for DUE LIMIT
- 8063 - To Change Storage Location Name
- 8066 - To test credit limit in testing Tenant
- 8082 - To create new storage location for Millco
- 8186 - To create new storage location
- 8241 - Create payment term creation
- 8254 - Not Allow for Post Automatically Only COA 21730000
- 8303 - To create new storage locations
- 8345 - New payment term creation
- 8380 - Transfer New Business Roles to Testing/Production Tenant
- 8397 - Create new customer group 1, 2, 3
- 8444 - To create new storage location
- 7397 - Error Message on tax code
- 7422 - Foreign currency valuation for bank not posted in GL
- 7513 - Period 10 was not opened
- 7534 - Unable to key in billing plan is SO, and unable to access PO
- 7569 - To create new storage location for ASIC
- 7594 - Period 11 not open as scheduled
- 7596 - Create Incoming/Outgoing Invoices - Menu Layout
- 7608 - Access to create payment term
- 7630 - Unable to key in billing plan is SO for 2nd line item
- 7774 - Open Period for 2026 P1 company code 1310
- 7787 - query on message prompt
- 7825 - Vessel name was cut off for Final Invoice's COO and PL
- 7837 - Not able to schedule recurring posting periods
- 7855 - Revaluation of foreign currencies balance to SGD (Functional Currency)
- 7858 - process 1 unable to create new SO
- 7862 - Automatic Account Determination
- 7894 - Start of new fiscal year – reset of journal entry sequential numbering
- 7935 - To create new storage location for PyinSa
- 7943 - Create bank statement
- 7989 - Duplicate invoice number due to reset of journal entry numbers in new fiscal year
- 8007 - Unable to key in billing plan is SO, for 2nd line item
- 8018 - Fwd: ACS Customer Statement (SAP 13) – New Form Customization and CR Scope,Mockup
- 8032 - The running order of the PBD items is incorrectly arranged.
- 8055 - Issue with Service Entry Sheet Approval
- 8062 - Storage Location Name of 01SP is wrong
- 8076 - New configurations
- 8093 - New Account add for Actual Costing Run_MAI
- 8114 - PO Terms and condition typo
- 8144 - Create segment, profit-center and cost-center for ACT (1210)
- 8149 - PO Terms and condition typo
- 8164 - S4 check for duplication of invoices in Manual and RPA
- 8173 - Invoice Packing List and COO not enough display word count
- 8183 - TR#AVYK900288 - Transport new GL account
- 8189 - PO - No Description
- 8190 - GL COA (AVYK900291 & AVYK900293)
- 8201 - Allow Postings to G/L accounts with open item management
- 8204 - Purchase Order Item Text alignment issue
- 8264 - Unable to Amend WBS Element in Sales Order – Assistance Required
- 8323 - To create new storage locations
- 8325 - Import custom query into production tenant
- 8337 - Import custom query into production tenant
- 8340 - New COA 07.05.2026
- 8352 - Query to SAP: Inability to Save Custom Layouts in "G/L Account Line Item Display G/L View"
- 8356 - Query on Upload Customer Line Items
- 8384 - Transport Request for COA Description Change
- 8411 - Request to Update Company Address for Wisarra (1200)
- 8427 - To create a new distribution channel
- 8445 - To Create & Rename Customer gp1,3
- 8453 - House bank reflected incorrectly in the customer invoice
- 8457 - Import version 102 into production tenant
- 8470 - Create new customer group 3
- 8471 - Purchase Order Header's Custom Field - Impact Fee Checkbox and Purchase Order Output Form Requirement
- Show Remaining Articles (58) Collapse Articles
Table of Contents
< All Topics
Print
8189 – PO – No Description
Issue Summary: [8189] The description entered in the PO field does not appear on the Purchase Order due to incorrect data entry.
Resolution / Workaround: The user was advised to enter the description data in the correct field, which resolved the issue. The root cause identified was that the user had entered the description data in the wrong field.