domingo, 4 de fevereiro de 2018

SAP S/4HANA 1709 – sneak preview

SAP S/4HANA Enterprise Management OnPremise version 1709 is awaited with eager eyes.
Reason – It is promising version with multiple changes and NEW innovations across Line of business (LOB)s.
With 1511 and 1610 versions of S/4HANA Enterprise Management, building blocks were laid down, with some CORE data-model changes, FIORI Analytical Applications, VDM’s starting of Integrated / Embedded Solutions.
With 1709 version, the journey strengthens it’s stack of Innovations, primarily in the new dimension technologies, supporting EDGE Usecases with IoT, Machine-Learning, Big Data Analytics to name a few.

Source SAP

With 1709, as SAP continues to consolidate the product-stack to  “One CORE” – (CRM as add-on, Commodity Management and so on),  the Innovations in Enterprise Management version are primarily based on EDGE technologies
This comes as big boost for “wait-and-watch” eyes, ( equally applicable to SAP’s Install based client as well as Implementation and Support partners ), who have been preparing for, planning for, wanted to understand, work-out usecases, business case for driving  the discussions on  “#DIGITAL TRANSFORMATION” and the “New Business Process”, New Business Models .
Source SAP

Also for those looking for Landscape Simplification and Consolidation, this version has certain features which forms as BASE for the journey ahead. (CRM as add-on, SAP for Industries, TM & EWM in Core is a Big-ticket item for many)
Source SAP

For those who are interested in L1 level Details of what’s expected in 1709, the NEW Innovations,  has already shared a crisp blog : S4HANA 1709 First Glance
https://blogs.sap.com/2017/07/25/first-glance-at-sap-s4hana-1709/


My PoV on 1709 : Can we say we have reached MID-WAY of the Journey towards the product expected in end 2019 – ” THE Digital CORE” and the initial stages of journey and platform for  S/4HANA Suite of products (expected to be  launched year on year till 2025) ?

Well, It would be interesting to know

(1) How early adopters of SimpleFinance, ( the in-flight project,) are reacting to S/4HANA Enterprise Management – 1709 ?
(2) Small and medium business – what are their views on S/4HANA Cloud and On-Premise deployments? Their adapability for contineous change and appatite and adoption of NEW Innovations .

Fonte: https://blogs.sap.com/2017/07/26/sap-s4hana-1709-sneak-preview/

Credit Management

All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
  • SM30 – Table/View
  • V_TVTW – Define Distribution Channel
  • V_TVTA_KKB – Assign sales area to credit control area
  • V_T014 – FI – Define Credit Control Area
  • T001CM – FI – Assign Permitted Credit Control Area to company code
OVXG – Set up Sales Areas
e.g. Sales Organization
Distribution Channel
Division
Distribution Channel
Division
FD32 – Customer Credit Management
OVAK – Define credit limit check by sales document type
  • Check Credit
    • A – Credit limit check and warning message
    • B – Credit limit check and error message (no sales order can be created)
    • C – Credit limit check and delivery block (block delivery if hit credit limit)
      • Options B and C -> used for checking open order values (when you create/change the sales order)
    • D – Automatic credit control with open order values
      • More control in transaction OVA8 – Automatic credit control
      • You check for open orders and deliveries, or just open deliveries.
      • or open order values with other options
  • Credit group
    • Allows you to combine different sales document types for the credit limit check
VKM1 – Blocked SD Documents – Finance have to released the delivery block
OVAD – Define credit limit check by delivery order
  • whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 – Define credit limit check by item category
  • Set whether to include/exclude item category for credit limit check
OVA6 – Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit management and define the (D – automatic credit check).
  • SAP default credit groups
    • 01 – credit group for sales order
    • 02 – credit group for delivery
    • 03 – credit group for goods issue
OVA8 – Automatic credit control – Double click on the line itemsYou can have the followings credit limit check :-
  • Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
  • Open items
No of days open
Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.Max open items %
The customer balance must not exceed a certain percentage.
  • Oldest open items
If you don’t want to deliver to the customer at all when even only 1 invoice is overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.Days oldest item
No of days allowed for overdue or payment terms.
Use of the credit check Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be reblocked again by the system. The system only reblocks the sales document if the new order quantity is above a certain % amount.
  • Released documents are still unchecked
The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
  • Next Review Date
If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document day is in April then the credit limit is zero.You can use the “NextReview date” and “Number of days” fields and combined it with the “Last int.review” field in customer credit master “Status” view (FD32).
VOKR – Display of work list for credit management (configure the display variant)
Releasing the Credit Block
These are the three transaction code you can used for releasing the SAP credit management block.
VKM3 – Sales Order
VKM5 – Delivery Order
VKM4 – Both Sales Order and Delivery Order
Useful SAP Credit Management program
RVKRED06 – Background jobs for checking blocked credit management.
If an order is no longer outside the horizon as defined in the dynamic credit check, (i.e. it is INSIDE the horizon) it can cause existing “good” orders to block. If you run this job every night, if you have your horizon set for 1 month it can cause a lot of blocks at beginning of month. Try to use ‘W’ for weekly horizon status.
RFDKLI10 – Customers With Missing Credit Data
RFDKLI20 – Reset Credit Limit for Customers
RVKRED77 – Reorganize SD credit data
When updating errors occur, it enables you to reorganize the open credit, delivery and billing document values.
RVKRED08 – Checking sales documents which reach the credit horizon
You should runs this report periodically, usually at the start of a period. The report checks all the sales documents, which reach the dynamic credit check horizon. The period for the ‘date of the next credit check’ is proposed from the current date, with the help of the period split for open sales order values.
Static and Dynamic Credit Check
Tell me the difference between Static and Dynamic Credit Checks. 
What is the difference between the Open Order Value used in Static check and the one used in Dynamic Check?
*Simple Credit Check :*
Tr.Code – FD32
It Considers the Doc.Value + Open Items.
Doc.Value : Sales Order Has been saved but not delivered
Open Item : Sales Order has been saved , Delivered, Billed & Transfered to FI, but not received the payment from the customer.
*Static Credit Check*
it checks all these doc value & check with the credit limit
1) Open Doc.Value / Sales Order Value : Which is save but not delievered
2) Open Delivery Doc.Value : Which is delivered but not billed
3) Open Billing Doc.Value : Which is billed but not posted to FI
4) Open Item : Which is transfered to FI but not received from the customer.
*Dynamic Credit Check*
1) Open Doc
2) Open Delivery
3) Open Billing
4) Open Items
5) Horizon Period = Eg.3Months
Here the System will not consider the above 1, 2, 3 & 4 values for the lost 3 months.
Settings for SAP FI Credit Management
The Credit Control Area is an organizational unit that represents an area responsible for granting and monitoring credit. Credit information can be made available per customer within a credit control area. One will use one credit control area that is four characters “JHEN”. All of the available functionality for credit management will not be used since a service has already been provided.
Stopping the billing process is not an option Organizational unit in an organization that specifies and checks credit limits for customers. A credit control area can include one or more company codes. It is not possible to assign a company code to more than one credit control areas. Credit and risk management takes place in the credit control area.
4.6x
OB45 – Maintain Credit Control Area
A company code can be assigned to one credit control area. However, a credit control area can be assigned to more than one company code.
OB38 – Assign Company Code to Credit Control Area.
If your company have different business area, you can assign each with a Credit Control Area. e.g. 0001 for BA-A, 0002 for BA-B, 0003 for BA-C etc. In this case, the same customer master code can have different credit limits for the different Business Area.
OB01 – Define Credit Risk Categories.
OB02 – Define Account Clerk Groups
OB51 – Define Credit Representatives
OB39 – Define Intervals for Days in Arrears for Credit Management
Fonte: https://sapsdforum.com/2007/10/23/credit-management/

Stock Transport Order - STO

Overview

STO is the intracompany process to transfer materials, between one plant to another within the same company with the same company code.

Customizings for STO
  • You have to register the supplying plant as a supplier and the receiving plant as a customer.

    The supplying plant can be customized on the vendor master data.
  1. XK03
  2. Enter the information of the supplying plant
  3. Select Purchasing Data and press enter
  4. Go to Extras
  5. Select Add. Purchasing Data
  6. See image below for reference:
The receiving plant can be customized following the path on SPRO:
  1. Materials Management
  2. Purchasing
  3. Purchase Order
  4. Set Up Stock Transport Order
  5. Define Shipping Data for Plants

                                                                                                 

______________________________________________________________________________________________________
Table J_1BIM02V should be set as below for movements 86X:

 
______________________________________________________________________________________________________
OMJJ - In this transaction you can set the allowed transaction for each movement, field settings, etc.

 
______________________________________________________________________________________________________
Tax Code Configuration on J1BTAX - MM
______________________________________________________________________________________________________
Posting String Configuration 
  1. J1BTAX
  2. Nota Fiscal
  3. Inventory Management
  4. IM Posting Strings
  5. Select the value string and make sure the option 'line item ID' is set to T - Tax or D - Tax.

Standard Process Flow

ME21N - Generate the Stock Transport Order

Use the order type 'UB' and Item Category should be set as 'U'.


VL10B - Create delivery
Fill the Purchasing document field and press Execute (F8):



Select the line click on Background:
 
Delivery will be created and you can now double click on delivery number created under 'Document' column:

Click on 'Edit/Change'(F1), then in 'Picking' tab fill the value in Picked Qty and all other necessary and relevant information. 



VL02N or VL03N - Change/Display Outbound Delivery
Enter the delivery created and press enter, then go to document flow (F7) to see an overview of documents created and it corresponding status. 



J1B3N - Display Nota Fiscal
The DOCNUM should come up automatically just enter the NF to see all the values of the NF created. 



MMBE / MB5T - Check goods movement
With these transactions, you can check the material's current situation. In this case, if the stock is in transit or if it was already delivered and free.
Here we can see an example of the system showing all the information about the material per Storage Location: 



Another alternative is MB5T:



With this transaction, you can see all the Stock in transit as shown below:



MIGO - Goods Receipt and incoming Nota Fiscal
Fill the outbound delivery number and enter movement 861.
Check items and mark them as ok and then post document.  
You can check the Nota Fiscal if you wish just by clicking on NF button.

Debug Tips

  • SE80>>>Function Group>>>J1BN>>>Function Module>>> J_1B_IM_TX_CALCULATE_TAX_NEW
    For all calculation routines related to material movement can be see in this FM and it is where it starts the interface with FI.
  • SE37>>>Function Module>>> CALCULATE_TAX_ITEM
    Where the KOMP and KOMK will be filled. 
  • SE80>>> Function Group>>>J1BF>>>Include LJ1BFF01 
  • In this include the NF is created. 
  • SE80>>> Function Group>>>MBGB>>> Subroutine>>> FORM AUSGABE (INCLUDE LMBGBFSU)
    This include you can find out issues regarding accounting posting and the famous balance error. 

Related Documents

Stock Transfer Order (STO) with Full or Partial Return of Transit Stock

Check out the SCN post in Portuguese about STO scenario for additional information.

Check out the SCN post in English about STO scenario for additional information


Related Notes/KBAs

123124
123124 - LSA BR:5th v. Customizing of Brazilian movement types
*This note delivers the report CATT P40XXXX_CU_BR to set all the Brazilian movements to its standard settings.
2149094STO - Changing tax code during Goods Receipt, at MIGO
2164657STO - Changing tax code during Goods Receipt, at MIGO
1650850Message error 8B122 when use transaction MR8M
1650880Subcontract Process Supported for Brazil Localization
1294597Nota Fiscal generation for inbound delivery
2078053Automatic determination of Incoterms for all Nota Fiscal processes
1890828Message "8B 146" - Enter a partner type, a partner function, and a partner iden
2069453MB1B- Incoterm is not being filled automatically for movement type 833
2069463Encapsulation of inbound delivery check
2038744Incoterms not filled automatically for mvt 541
1768008Subcontracting: Configuring acc.keys for different acc.
2037109Subcontracting: Balance error in reversal process for mvt. 542
2055635LPP: Incoming nota fiscal (GR) generated with wrongly values for STO process
2062152LPP: Incoming nota fiscal (GR) generated with wrongly values for STO process
679372DIFAL - Brazil: Tax on goods movements - Customizing
722167BR: Altn. base amt and ctrl ind. for BAPI_GOODSMVT_CREATE
1907014Future Delivery - Canceling a document with foreign currency
2012645STO: Goods Receipt error on MIGO using Inbound Delivery
1977720Subcontracting: Reversal document generated by mvt. 544 did not generate taxes
2000223Subcontracting: Reversal document generated by mvt. 544 did not generate taxes
1640802Stock Transport Order between project stocks
1677806Allow tax calculation for subcontracting process

Fonte: https://wiki.scn.sap.com/wiki/display/LOCLA/Stock+Transport+Order+-+STO