SAP was accused of stealing customer support documents and software
Read report at http://www.msnbc.msn.com/id/40344534/ns/business-us_business/
Wednesday, November 24, 2010
Thursday, April 22, 2010
Delivery Order: Actual Goods Movement date
To post goods issue a delivery order document (VL02N) to a specific date, enter the date in the Actual Goods Movement Date field.
SAP Help: Actual goods movement date
You can preset the posting date for goods movement with the actual goods movement date. For example, if the posting should occur in a previous period or month, you can do so with this default.
SAP Help: Actual goods movement date
You can preset the posting date for goods movement with the actual goods movement date. For example, if the posting should occur in a previous period or month, you can do so with this default.
Labels:
Tips
Monday, March 29, 2010
Monday, March 8, 2010
Maintain SAP System Message: Shipping
Transaction Code OVM1.
Message type - shipping processing:
. ' ' No notification
. 'I' Background: conditional log / Dialog: info message
. 'W' Background: no log / Dialog: warning
. 'E' Background: System reaction + log / Dialog: error
Message type - shipping processing:
. ' ' No notification
. 'I' Background: conditional log / Dialog: info message
. 'W' Background: no log / Dialog: warning
. 'E' Background: System reaction + log / Dialog: error
Labels:
Tips
Friday, January 15, 2010
Define Reconciliation Accounts Without Credit Management Update
Define Reconciliation Accounts Without Credit Management Update
Source SAP HELP
In this IMG activity, you can cancel the credit management update function for certain postings by posting to an additional reconciliation account; the reconciliation account without credit management update.
When you make postings to the standard reconciliation account, the receivables total within credit management is then updated, but those postings made to the reconciliation account without credit management update are not.
SPRO Menu: Financial Accounting > Accounts Receivable and Accounts Payable > Credit Management > Define Reconciliation Accts Without Credit Management Update
Transaction code AKOF
Source SAP HELP
In this IMG activity, you can cancel the credit management update function for certain postings by posting to an additional reconciliation account; the reconciliation account without credit management update.
When you make postings to the standard reconciliation account, the receivables total within credit management is then updated, but those postings made to the reconciliation account without credit management update are not.
SPRO Menu: Financial Accounting > Accounts Receivable and Accounts Payable > Credit Management > Define Reconciliation Accts Without Credit Management Update
Transaction code AKOF
Labels:
Tips
Wednesday, October 7, 2009
Check for deleted documents in SAP
To check for deleted documents in SAP, view table CDPOS.
Table:
CDHDR (Change document header)
CDPOS (Change document items)
Change doc. object
. LIEFERUNG
Table Name
. E.g Delivery Order tables LIKP, LIPS
Change ID
. U - Update
. I - Insert
. E - Delete (single field documetation)
. D - Delete
Table:
CDHDR (Change document header)
CDPOS (Change document items)
Change doc. object
. LIEFERUNG
Table Name
. E.g Delivery Order tables LIKP, LIPS
Change ID
. U - Update
. I - Insert
. E - Delete (single field documetation)
. D - Delete
Labels:
Tips
Wednesday, August 5, 2009
Cost Center Field In Sales Order Transaction VA01
Assign Cost Center by sales order reason
. Transaction: OVF3 Assign Cost Centers
If the Order Type's SD document category (VOV8) is set to "I" (Order w/o charge), than the Cost Center field in the Sales Order (VA01) will be active.
. Transaction VOV8 Sales Document Type
. Transaction: OVF3 Assign Cost Centers
If the Order Type's SD document category (VOV8) is set to "I" (Order w/o charge), than the Cost Center field in the Sales Order (VA01) will be active.
. Transaction VOV8 Sales Document Type
Labels:
Tips
Friday, December 12, 2008
Duplicate Purchase Order Number (VBAK-BSTNK) in Sales Order
Same Purchase Order number (VBAK-BSTNK) in Sales Order
The Sales order type xxx "Check purchase order number" is set to "A" (TVAK-PRBST) (Check whether the purchase order number already exists).
Screen: SPRO Sales order type
SCENARIO:
. Open two sessions
. Create sales Order 1 and sales order 2 with the same Purchase Order number at the same time.
. Do not save both orders until both are completed.
. Save order 1 and than save order 2.
. No message "Purchase order number in document & already exists"
SOLUTION:
As long as the document is not saved in database, the R/3 system does not know that the purchase order number already exists.
In SD, there is no buffer table where the temporary purchase order number is stored, in order to check if one already exist. This would impact system performance. As a result, the scenario above is R/3`s standard system behavior.
NOTE:
The standard SAP system behaviour in checking purchase order number:
Case 1:
Create two orders with the same order type, the same sold-to and the same purchase order number.
-> Message V4 115 "Purchase order number in document & already exists" appears
Screen: Sales order message V4 115
Case 2:
Create two orders with different sold-to parties, same order type and same purchase order number.
-> No message V4 115.
Case 3:
Create two orders with different order types, same sold-to and same purchase order number.
-> No message V4 115.
The check purchase order number is validated via the following selection criteria:
. Customer Number
. Sales Order Type
Reference Program Code:
. SAPFV45K
. FV45KF0V_VBKD-BSTKD_PRUEFEN
The Sales order type xxx "Check purchase order number" is set to "A" (TVAK-PRBST) (Check whether the purchase order number already exists).
Screen: SPRO Sales order type
SCENARIO:
. Open two sessions
. Create sales Order 1 and sales order 2 with the same Purchase Order number at the same time.
. Do not save both orders until both are completed.
. Save order 1 and than save order 2.
. No message "Purchase order number in document & already exists"
SOLUTION:
As long as the document is not saved in database, the R/3 system does not know that the purchase order number already exists.
In SD, there is no buffer table where the temporary purchase order number is stored, in order to check if one already exist. This would impact system performance. As a result, the scenario above is R/3`s standard system behavior.
NOTE:
The standard SAP system behaviour in checking purchase order number:
Case 1:
Create two orders with the same order type, the same sold-to and the same purchase order number.
-> Message V4 115 "Purchase order number in document & already exists" appears
Screen: Sales order message V4 115
Case 2:
Create two orders with different sold-to parties, same order type and same purchase order number.
-> No message V4 115.
Case 3:
Create two orders with different order types, same sold-to and same purchase order number.
-> No message V4 115.
The check purchase order number is validated via the following selection criteria:
. Customer Number
. Sales Order Type
Reference Program Code:
. SAPFV45K
. FV45KF0V_VBKD-BSTKD_PRUEFEN
Labels:
User's Query
Subscribe to:
Posts (Atom)