米列史丹

Please follow these steps: Step1. Add new fields in the structure RFPOS; Step2. To fill your new fields you active the BTE 1650: you have to copy the fm SAMPLE_INTERFACE_00001650 and here insert abap code to fill the new fields. By trx FIBF: Setting->Event: here insert the name of your fm for event 1650. Step3. Run the report RFPOSXEXTEND: this report will arrange the structure RFPOSXEXT based on definition of RFPOS. Remember this modifications are available  for all kind of items: so G/L (trx FBL3N) , Receivable (trx FBL5N) and Payable FBL1N. So in your fm check the field KOART: KOART = 'S' ->G/L KOART = 'D' ->Payable KOART = 'K' ->Receivable

My question: After changing some fields, PO texts will disappear. Please refer to SAP NOTE: 367224. Solution Implement the following notes in your system (if they are valid for your release). Implement these notes even if they do not describe your problem exactly. 215138, 213250, 323257, 326029, 331575, 352320, 357972, 362300, 366658 Note the following: ----------------------------- When you enter certain values, the texts are transferred again from the master records or reference documents. As a result, texts that are entered manually are overwritten or deleted. The relevant values are listed below. Header texts are determined again if the following values change: Language Vendor Purchasing organization Contract (of the first item) Request for quotation (of the first item) Reference purchase order (of the first item) Item texts are determined again if the following values change: Language Material Purchasing info record Plant (if a purc...

Possible cause 1:  GR posting month of inspection lot is not opened, so after execute BAPI, it will be error QV 054:  Error during quantity posting for inspection lot xxxxxxxxxxxx, manual proc. Required   Possible cause 2:  SAP NOTE: 1959967 Reproducing the Issue Execute add-on program which calls BAPI_INSPLOT_SETUSAGEDECISION, sometimes error QV 054 happens. Cause Statements like "commit" and "commit work" is used in customer own coding. These could cause possible inconsistencies. Resolution Please make sure there is no statements like "commit" and "commit work" in your own coding. See Also Report ZQEVAC22 in note 174877 should help detect and correct the UD code inconsistency.