Data archiving: purchase requisitions

This blog will explain how to archive purchase requisitions via object MM_EBAN. Generic technical setup must have been executed already, and is explained in this blog.

Object MM_EBAN

Go to transaction SARA and select object MM_EBAN.

Dependency schedule:

No dependencies.

Main table that is archived:

  • EBAN (Purchase requisitions)

Technical programs and OSS notes

Pre-processing program: RM06BV70

Write program: RM06BW70

Delete program: RM06ID70

Read program: RM06BR30

Relevant OSS notes:

Application specific customizing

In the application specific customizing for MM_EBAN you can maintain the document retention time settings:

You have to set the residence time per requisition type:

Preprocessing

In transaction SARA, MM_EBAN select preprocessing:

There are quite some reasons why a purchase requisition cannot be archived.

Executing the write run and delete run

In transaction SARA, MM_EBAN select the write run:

Select your data, save the variant and start the archiving write run.

Give the archive session a good name that describes the purchasing group and year. This is needed for data retrieval later on.

After the write run is done, check the logs. MM_EBAN archiving has average speed, and medium percentage of archiving (50 to 90%).

Deletion run is standard by selecting the archive file and starting the deletion run.

Data retrieval

For MM_EBAN start the read via SARA:

Then select the archive file(s).

Result is in a simple list:

Data archiving: WM transfer requirements and orders

This blog will explain how to archive WM transfer orders and requirements via objects RL_TA and RL_TB. Generic technical setup must have been executed already, and is explained in this blog.

Objects RL_TA and RL_TB

Go to transaction SARA and select object RL_TA and RL_TB.

Dependency schedule (no dependencies for both):

Main tables that are archived:

  • LTAK (transfer order header)
  • LTAP (transfer order item)
  • LTBK (transfer requirement header)
  • LTBP (transfer requirement item)

Technical programs and OSS notes

RL_TA:

Write program: RLREOT00S

Delete program: RLREOT10

Read program:RLRT0001

RL_TB:

Write program: RLREOB00S

Delete program: RLREOB10

Read program: RLRB0001

Relevant OSS notes:

Application specific customizing

RL_TA and RL_TB don’t have application specific customizing.

Typically RL_TA and RL_TB will yield 90 to 100% documents that can be archived.

Executing the write run and delete run

In transaction SARA, RL_TA or RL_TB select the write run:

Select your data, save the variant and start the archiving write run.

Give the archive session a good name that describes sales warehouse and year. This is needed for data retrieval later on.

After the write run is done, check the logs. RL_TA and RL_TB archiving has average speed, and a high percentage of archiving (up to 90 to 100%).

Deletion run is standard by selecting the archive file and starting the deletion run.

Data retrieval

Start the data retrieval program and fill selection criteria for transfer orders:

Start the data retrieval program and fill selection criteria for transfer requirements:

In the popup screen select the wanted archive files.

SREPO: compare multiple sources across systems

SREPO is a tool to compare multiple ABAP code programs across 2 systems.

The background can be found in OSS note 1368474 – System comparison tool SREPO Version 2.0.

Using SREPO tool

Start transaction SREPO. Enter the RFC between the 2 systems and the list of objects to compare:

Then press the button Object Intersection. Result list is a list of programs existing in either one or both the systems:

Select a single program and start the Version Comparison:

SAP Solution builder

The S4HANA SAP solution builder can be used to generate SAP best practice content in your S4HANA system as a quickstarter.

Questions that will be answered in this blog are:

  • How to activate SAP solution builder?
  • How to activate a specific solution building block?

Updating solution builder

By default the solution builder is already present. The content is regularly updated. So before starting with the solution builder, read and follow the instructions:

2914416 – SAP S/4HANA 2020 collective note for content activation

3053781 – SAP S/4HANA 2021 collective note for content activation

3199321 – SAP S/4HANA 2022 collective note for content activation

They will refer to content to be uploaded, OSS notes to apply.

Activation of content

Start the solution builder with transaction /SMB/BBI:

First load the data: menu option Solution/ import / global meta data / From reference content.

Now we want to import reference content for specific country. From menu options choose Solution / import / Solution (XML) / From reference content:

In this case we choose US. Now wait until the building blocks are loaded.

From this template we will make a copy to run with limited blocks. First select the copy button and enter the details:

Important now: set this copy to your favorite with the button!

Double click on the solution. Use the tick boxes to set the desired scope:

You can check if you want by clicking the Building Block Builder button that indeed only this content is present now:

On the empty icon on the right you can see the data is not yet loaded:

Select from the menu option Solution / Import / Installation data / From reference content. Wait again and refresh screen. Data should now be loaded.

With the data loaded we can now click on the button Implementation Assistant to start the activation process.

Select the activate button:

Press enter in this screen:

Activation will run.

Check the results:

In SE10 you can find your transport with the customizing activities performed.

Background reference

OSS note 3126942 – Jump Start Your SAP S/4HANA 2021 Implementation by Activating SAP Best Practices contains an excellent description of all the steps and at the end a detailed list of knowledge OSS notes for specific topics of the solution builder.

For SAP help reference click here.

Linux versions and support for Linux

Many SAP system use Linux as operating system.

It is important that you check you run a supported combination of Linux OS, database and application.

SAP HANA OS support

For SAP HANA database, the master note is 2235581 – SAP HANA: Supported Operating Systems. This note contains the references to all the version specific OSS notes.

Checking kernel and LINUX version in SAP system

To check your kernel and LINUX version, go to System Status and then open the Other Kernel Info button:

Another option is to run function module TH_SAPREL3 in SE37:

Translating the version

You have to use the RedHat or SUSE site to translate the kernel number into the LINUX OS version.

Example:

This version

Translates to:

So RedHat version 8.7.