米列史丹

1. service.sap.com/            → 下載notes的txt檔 2. TCODE: SNOTE 做txt上傳

BAdI: BOM_UPDATE Method: CHANGE_AT_SAVE [CODE] METHOD IF_EX_BOM_UPDATE~CHANGE_AT_SAVE.   CHECK SY-TCODE EQ 'CS02'.   DATA: WA_STPO TYPE STPO,               L_MATNR TYPE MAST-MATNR,               L_WERKS TYPE MAST-WERKS,               L_STLNR TYPE MAST-STLNR,               L_STLAL TYPE MAST-STLAL,               TB_STPO TYPE STANDARD TABLE OF STPO,               L_RELEASE(1) TYPE C,               WA_STKO TYPE STKO,               WA_MAST TYPE MAST,               WA_STPO2 TYPE STPO.   CLEAR L_RELEASE.   LOOP AT DELTA_MASTB INTO WA_MAST.     MOVE: WA_MAST-MATNR TO L_MATNR.     MOVE: WA_MAST-WERKS TO L_WERKS.   ...

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.

[PURPOSE]   Check whether the payment term is suitable for the customer or not in VA01/VA02. [TOOL]   INCLUDE: MV45AFZZ USEREXIT: USEREXIT_SAVE_DOCUMENT_PREPARE XVBAK ← New data if any change/else it will be same as old YVBAK ← Old value VBAK ← Work area when you deal with Items it will be some thing like this.. XVBAP ← New data if any change/else it will be same as old YVBAP ← Old data if any change(considers item) /else it is blank If we want to get SO header where in header or items, we can obtain from WA: VBAK does not concerned to use XVBAK or YVBAK or OVBAK. [CODE] FORM USEREXIT_SAVE_DOCUMENT_PREPARE.   DATA: P_ZTERM TYPE KNB1-ZTERM,                P_MESSAGE TYPE STRING. ** GET PAYMENT TERM IN CUSTOMER MASTER DATA   CLEAR P_ZTERM.   SELECT SINGLE ZTERM INTO P_ZTERM FROM KNVV WHERE KUNNR = VBAK-KUNNR                       ...