openSAP: Gain Experience with Business Partner for SAP S/4HANA Conversion
Customer/vendor integration overview: phases and CVI cockpit
Posts
ABAP development for Accounting [rev]
2083799 - Composite SAP Note: Postings with Accounting BAPIs 1232484 - How to use the VAT due date, tax reporting date VATDATE 1232484 - How to use the VAT due date, tax reporting date VATDATE The functionality is based on legal requirements in different countries. Incomplete list of countries currently known: Poland, Hungary, Slovakia, Spain. For each country it must be checked whether the functionality fulfills the legal requirements. 1. Activation of the functionality The functionality can be activated per company code in the usual customizing for the company code 'Enter Global Parameters'. (transaction OBY6 or SM30: View V_001_B) For this purpose the new field XVATDATE has been added to table T001. 2. General rule If the functionality is active then every financial accounting document that is tax relevant ( i.e. contains a tax code in a g/l-line item) must have a valid date in the field VATDATE. If the document is not tax relevant, or the functionality is off in the company
openSAP: S/4HANA Embedded Analytics
Introduction, Overview, and Business User Introduction, Overview, and Business User Virtual data model – Principles 1. Naming rules for CDS models and element names . For instance, the VDM view I_CostCenter represents the cost center entity in all SAP S/4HANA applications. 2. Enforcement of unambiguous element names through global technical names catalog (GFN). Thus, the element CostCenter represents the cost center identifier in each and every model it is used in. 3. Specification of purpose of CDS views : analytical dimension, cube, search model, text, value help etc. 4. Strict specification of the model lifecycle – Stability contracts: if a view is safe to use in customer development – Deprecation workflow: if a view or an element of a view should no longer be used and what to use instead. Basic interface views ▪ Represent the core business entities of the SAP S/4HANA system ▪ Designed very close to the database tables – can be used instead of the table without performance penaltie
Status management [REV]
Status management allows to document the current processing status of an object, such as a sales order or sales order item. The current processing status can consist of a combination of individual statuses. Each individual status fulfills two functions: It informs you that a particular status has been reached (for example: "Sales order has been released") It determines which business transactions may or may not be carried out next (for example: Delivery is allowed, billing is not) There are two kinds of status: System status User status System statuses are determined automatically by the transactions you carry out. You cannot change a system status manually. Function: STATUS_CHANGE_FOR_ACTIVITY You can assign several user statuses at the same time. Use in Sales User statuses, on the other hand, can be activated and deactivated by the user. Individual user statuses can be grouped together into status profiles. The status profiles can then be assigned in Customizing for Sale