> For the complete documentation index, see [llms.txt](https://docs.prebilt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prebilt.com/prebilt-for-im-wm-strm/enhancing-prebilt/integration-with-amd-and-cfg.md).

# Integration with AMD and CFG

App Master Data (AMD) and Config (cfg) act as an integration layer between the frontend and the backend which allows for customisation from functional and technical consultants without needing to make

## AMD

Opening the AMD transaction */TCTM/WM\_CFG\_D* will show the following screen. Entering a transaction and executing will show the following AMD for said transaction.

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2FQEtbLg9TuwJ1rp7SzUeE%2Fimage.png?alt=media&amp;token=e747a58e-b803-41a2-86cb-a7a527f482d8" alt=""><figcaption></figcaption></figure>

For example this is the AMD for *PB2\_STK\_ENQ\_MAT\_IM*.

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2FpKUDWAsDRTJRhyWHxAhK%2Fimage.png?alt=media&amp;token=1e6fc72b-547a-4a80-8b61-ff18915ba9fe" alt=""><figcaption></figcaption></figure>

Each transaction will have its own configuration depending on what functionality we want the app to have. However, there are some common ones that we see across most apps.

More information can be found [here](/prebilt-for-im-wm-strm/app-master-data/screen-framework.md).

## CFG <a href="#toc214462475" id="toc214462475"></a>

When opening transaction */TCTM/WM\_CFG*, you’ll be greeted with the following screen, although the warehouses, transactions codes etc will differ depending on which system and client you are logged into.

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2FGEYzGE5dwd2KfDSHioap%2Fimage.png?alt=media&amp;token=2ab9438a-7fb9-43dc-bf9c-9121f255ce10" alt=""><figcaption></figcaption></figure>

This is typically more of a functional scope but as a quick overview the Dialog Structure menu down the lefthand side contains the screens where we store and change information.

### Warehouse

Shows a list of each warehouse in this SAP environment.

### Menu <a href="#toc214462477" id="toc214462477"></a>

Selecting a warehouse and then clicking ‘Menu’ shows the menu structure for each app when we log into PreBilt.

For example in transaction LRFMD, my user is assigned to warehouse PB1 and menu PB2TEST00.

Which in cfg has the following menu structure:

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2FO2uQ6TgO0m2UM84vSq9V%2Fimage.png?alt=media&amp;token=6ac4f468-4e35-4077-9c16-191a2d39c0ad" alt=""><figcaption></figcaption></figure>

This is then reflected when we log into PreBilt with the same user/warehouse combination.

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2F9Y10HaYeIvyn8tLpSZJ1%2Fimage.png?alt=media&amp;token=4c93f689-6890-4fad-be59-8e1fa58df191" alt=""><figcaption></figcaption></figure>

Note: Each menu can then branch off into its own menus but ultimately we should end up at the transactions for each of the app we want to use in a given warehouse.

E.g., Menu PB2INB00 will show the Inbound transactions and PB2OUT00 will show the Outbound transactions.

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2F8DdrBz0Bmr8zsiT80Frz%2Fimage.png?alt=media&amp;token=f04281ef-f47c-4b7e-9030-427bfe65ab02" alt=""><figcaption></figcaption></figure>

### Transaction codes <a href="#toc214462478" id="toc214462478"></a>

This is where each transaction code points to the relevant service class in the backend. For example, all the General posting transactions point to the service class /TCTM/WM\_APP\_513.

There are also descriptions for what each transaction code is for.

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2F6OPl2PMEEKwEFKkbDks6%2Fimage.png?alt=media&amp;token=2395a0e7-3014-4eda-96de-cbf847c82e5f" alt=""><figcaption></figcaption></figure>

Custom enhancments: If we want to make a modification using a Z class in the backend (e.g., *ZTCTM\_WM\_APP\_510*) we would need to make sure this is changed in cfg so that we run the correct custom class when calling a specific transaction.

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2FPdwhzZCJlBPqqDsPdHjF%2Fimage.png?alt=media&amp;token=9f576bcd-8974-4fb3-9c44-1248f871faf8" alt=""><figcaption></figcaption></figure>

### Configuration fields

Selecting a transaction and clicking on configuration fields opens a blueprint for the layout we see in AMD. This is where we can view, amend, add or delete fields for the corresponding transactions AMD.

For example, this is the configuration fields for transaction *PB2\_STK\_ENQ\_MAT\_IM* that we saw earlier

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2FDaGWdpQbaGywCxkGtFjF%2Fimage.png?alt=media&amp;token=7378067c-b196-43d9-bccd-affe3e22a9af" alt=""><figcaption></figcaption></figure>

### Text Override

Again, selecting by transaction this will show the text overrides for each transaction. Typically, we see a TEXT no or TEXT-ID which has a corresponding value, therefore within our app where we want said value we can use the TEXT-ID rather than hardcoding it directly. The allows for greater consistency and can facilitate translations into other languages.