Have you ever been in a situation where you wanted to add a key user custom field to a given database table (e.g. ACDOCA or VBAK), but you did not know which business context to choose?
Or are you right in the middle of an ECC to SAP S/4HANA migration project, and you have legacy custom fields in your ECC system? You want to recreate custom fields in SAP S/4HANA, and you don’t know which business context to choose?
If your answer is yes, then this blog post is just for you. In this blog, you’ll find out how to determine the right business context based on a given database table name (or CI-include name or extension include name).
The ways to determine the right business context differ between SAP S/4HANA Cloud Public Edition and SAP S/4HANA Cloud Private Edition (and on premise).
Have you ever been in a situation where you wanted to add a key user custom field to a given database table (e.g. ACDOCA or VBAK), but you did not know which business context to choose? Or are you right in the middle of an ECC to SAP S/4HANA migration project, and you have legacy custom fields in your ECC system? You want to recreate custom fields in SAP S/4HANA, and you don’t know which business context to choose? If your answer is yes, then this blog post is just for you. In this blog, you’ll find out how to determine the right business context based on a given database table name (or CI-include name or extension include name). The ways to determine the right business context differ between SAP S/4HANA Cloud Public Edition and SAP S/4HANA Cloud Private Edition (and on premise). Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
