cancel
Showing results for 
Search instead for 
Did you mean: 

FI Validation and Substitution (GGB0 and GGB1) in S/4 Hana system

0 Kudos
7,433

Hello SAP Gurus,

I need to know how is working the process of Validation and Substitution on the S/4 Hana system.

In our actual SAP ERP we use the standard transaction

GGB0 and OB28---------> Validation.

GGB1 and OBBH--------->Substitution.

and then for a lot of them we have implemented user exit where we have written our z-code.

How look like in S/4 Hana this process? Will be always possible to user the transaction above and will always possible to implement a kind of user exit behind?

I tried to search a bit in Internet, I found some information under this link:

https://help.sap.com/viewer/4ebf1502064b406c964b0911adfb3f01/2020.000/en-US/5c8c2825535f4e3aa9b7f716...

But here is mentioning the App on Fiori, my question is more on S/4 HANA GUI. Do you know any official documentation or any information about that?

Thank you in advance.

Accepted Solutions (0)

Answers (3)

Answers (3)

0 Kudos

Hi,

please check the following note on background information for substitution/validation when posting accounting documents in S/4 Hana https://launchpad.support.sap.com/#/notes/3093515 .
GGB0 / GGB1 is still used in S/4 Hana OP. It is not used in the cloud. Usage could differ based on which business process / events you are talking about.

claudioserpa
Explorer
0 Kudos

Good Morning. I created validation rules in GGB0. When SAP GUI transactions are executed in Fiori, the program goes through the rule. FI-specific apps also work. However, when making a service entry, via the service sheet, it does not go through the rule, even meeting all the conditions stipulated in the rule.

Can you help me?

Thanks!

shwetanargachhe
Active Participant
0 Kudos

Hi

There is no difference in handling validation and substitution in S4 Hana on premise. Your testing scope increase to test application Via Fiori if any in scope.Ensure your screen on fiori aligned for mandatory fields from screen variants to ensure any validation errors can be addressed on fiori screen.

For GUi based applications there is no change.