Thứ Sáu, 22 tháng 7, 2016

T-Code: Post Vendor Invoice

1. MIRO - If you have Purchase Order details and your MM module is in place, then you can post. However, before posting MIRO, you should have Purchase Order in place ME21N and goods receipt must have been made in MIGO.
 
2. If it is pure FI Invoice, then you can post the invoice through F-43 or FB60
 
Now for any of the invoices 1 or 2, you would like to make the payment,
 
You can make the payment by using
 
F-53 - Creates Payment Document (To assign check manually use FCH5, to assign automatically use FBZ5)
F-58 - Creates the Payment document as well as assign the check automatically.
F110 - For Automatic Payment Program
 
If you want to void the check, then FCH9
If you want to void the check as well reverse payment document FCH8
 
If you have not assigned any check so far, but would like to reverse the payment document, then use FBRA.
 
Once you have reversed the payment, if you still wanted reverse invoice document, then use FB08.
 
If you want to see the check register, use FCHN.
 
To update the check number on assignment or reference field, you can use FCHU.

No suitable summarization level with data exists


No suitable summarization level with data exists
Message No. KN424

Diagnosis


The system attempted to read data from summarization levels. However, no summarization level suitable for the report could be found. Either no summarization levels were generated through data collection runs, or new fields were added to the data structure that are not yet in the summarization levels.


System Response
No data could be read.


Procedure
Execute the data collection run for the period you want to summarize:
Execute data collection for drilldown reports
When new fields are added to the data structure, such as through a release upgrade, then when a data collection is executed for a new period the new fields are added to the old dataset and given blank initial values.

SD Tables

 

Customers        
                  KNA1   General Data
                  KNB1   Customer Master – Co. Code Data (payment method, reconciliation acct)
                  KNB4   Customer Payment History
                  KNB5   Customer Master – Dunning info
                  KNBK   Customer Master Bank Data
                  KNKA   Customer Master Credit Mgmt.
                  KNKK   Customer Master Credit Control Area Data (credit limits)
                  KNVV   Sales Area Data (terms, order probability)
                  KNVI   Customer Master Tax Indicator
                  KNVP   Partner Function key
                  KNVD   Output type
                  KNVS   Customer Master Ship Data
                  KLPA   Customer/Vendor Link
                                  
Sales Documents   VBAKUK VBAK + VBUK
                  VBUK   Header Status and Administrative Data
                  VBAK   Sales Document - Header Data
                  VBKD   Sales Document - Business Data
                  VBUP   Item Status
                  VBAP   Sales Document - Item Data
                  VBPA   Partners
                  VBFA   Document Flow
                  VBEP   Sales Document Schedule Line
                  VBBE   Sales Requirements: Individual Records

SD Delivery Docume 
                  LIPS   Delivery Document item data, includes referencing PO
                  LIKP   Delivery Document Header data

Billing Document 
                  VBRK   Billing Document Header
                  VBRP   Billing Document Item

SD Shipping Unit  VEKP   Shipping Unit Item (Content)
                  VEPO   Shipping Unit Header

http://abap.sapland.com/references

OPEN DATASET

 

Code example to open dataset

DATA: file TYPE string VALUE `test.dat`.
OPEN DATASET file FOR OUTPUT IN TEXT MODE
ENCODING DEFAULT
WITH SMART LINEFEED.
TRANSFER `1234567890` TO file.
CLOSE DATASET file.

http://abap.sapland.com

Thứ Tư, 20 tháng 7, 2016

SAP Report Get Stock by Storage

Transaction Code:ZKGMB5B

In SAP, we can get Stock movement via MB5B standard report , but this report do not have option to run by storage location . To solve this problem, we can user ABAP Memory to get MB5B’s result and get data into own internal table via SUBMIT function.

 

Report: ZK_GET_MB5B:

IMPORT IT_TOTAL FROM MEMORY ID 'ZMB5B'.
FREE MEMORY ID 'ZMB5B'..


Enhancement : RM07MLBD
1

You can send letter to info@sapland.como to ask this code.

Thứ Tư, 5 tháng 12, 2012

Release History (Date & Time) of Sale Order


Author: Khoa Huynh
Web: www.sapland.com

Add Credit History to Reports

History of sale order changes is saving in Table CDHDR. For exactly information of credit status change, we can query this table with field Object “VERKBELEG” .

View Credit Status History of Single Sale Order

In sale to delivery process, usually sale order is blocked when customer do not have enough credit conditions and released this sale order need to be manually released via T-Code VKM1. There are 4 status of sale order:


To know exactly credit status of particularly sale order , first go to T-Code VA03:
Step 1:
Step 2:
On Sale Order Screen, go to Environment -> Changes Menu
Step 3:
Press F8 to run, the report show detail changes of SO. To view detail of change, select line and double click :
Example below show this order is release via T-code VKM1 at 15:47:30 by user htkhoa .