SAP Community - ABAP Development

Settlement BAPI "BAPI_CONDITION_CONTRACT_DOC_IN" Overwriting Custom AP Reference Numbers(REF_DOC_NO)

2026-04-05T14:59:50.289000+02:00

Hi SAP Community,
Facing a functional inconsistency where the settlement BAPI initially accepts the user-provided REF_DOC_NO value during validation but automatically overwrites it with the generated document number during the actual posting process for AP documents.

This works fine for AR but not AP.

How can we preserve the user-defined reference number? Is there a BAdI or parameter we're missing?

Any help appreciated!

Below are the parameters passed for the AP Document,

Header data:

Item data:

gCTS Developer Workflow Guide

2026-04-06T09:13:56.780000+02:00

For ABAP Developers Transitioning from Traditional CTS

1. GENERAL FLOW: DEV → QAS → PRD
Traditional CTS (What You Know)
DEV ──[Transport Request]──► QAS ──[Transport Request]──► PRD
(STMS) (STMS)

You create a transport request in DEV
You release it
Transport admin imports it into QAS via STMS
After testing, the same TR is imported into PRD
The transport request IS the delivery vehicle

gCTS (What Changes)
DEV ──[commit/push to Git]──► Git Repo ◄──[pull]── QAS
◄──[pull]── PRD

You still create transport requests in DEV (this doesn't change!)
When you release the transport request, gCTS automatically commits the changed objects to the Git repository
There is NO automatic import into QAS — someone must pull from Git into QAS
Same for PRD — someone must pull the desired commit/branch

Step-by-Step: A Normal Development Cycle
In DEV System (Developer's perspective — barely changes)

Open ADT (Eclipse), connect to DEV
Create/modify your ABAP object (class, CDS view, etc.)
Assign it to a transport request — yes, exactly like before
Do your development work
Release the transport task (your subtask) — same as before
Release the transport request — same as before

What happens behind the scenes at release:

gCTS detects the release
The Observer Job (a background job running in DEV) picks up the released TR
It serializes the objects and commits + pushes them to the remote Git repository
The commit message typically contains the TR number and description

Key difference: In traditional CTS, releasing a TR queues it for import via STMS.
In gCTS, releasing a TR triggers a Git commit. There's no STMS import queue.

Moving to QAS (Basis Admin or Release Manager)

Open the Git-enabled CTS Fiori app on the QAS system
Open the relevant repository
You see a list of commits (each one = a released TR from DEV)
Select the commit you want to deploy
Click Pull
gCTS deserializes the objects and imports them into the QAS ABAP system

Traditional CTS equivalent: This replaces the STMS import step. Instead of importing a specific TR, you're pulling a specific Git commit.
Moving to PRD (Same process)

Open Git-enabled CTS Fiori app on PRD
Open the repository
Pull the tested commit (or a release branch)
Objects are imported into PRD

What the Fiori App Shows You
┌─────────────────────────────────────────────────┐
│ Git-enabled CTS │
│ │
│ Repository: Z_MY_PROJECT │
│ Branch: main │
│ Current Commit: abc1234 │
│ │
│ Commit History: │
│ ┌─────────────────────────────────────────┐ │
│ │ def5678 - Fix ALV output - TR DEVK900123│ ◄──── Latest │
│ │ abc1234 - Add new report - TR DEVK900122│ ◄──── Current │
│ │ 789abcd - Initial setup - TR DEVK900121│ │
│ └─────────────────────────────────────────┘ │
│ │
│ [Pull] [Checkout Branch] │
└─────────────────────────────────────────────────┘

Current Commit = what's currently active in this system's ABAP runtime
Pull = bring a commit (and everything before it) into this system
You pull to a specific commit — all commits UP TO that point come in

2. BUG FIX FLOW: Fixing an Object in PRD
Scenario
Object ZCL_SALES_ORDER exists in PRD. A bug is found. Developer needs to fix it.
Does the ENTIRE object move, or just the delta?
The entire object moves. This is critical to understand.
AspectTraditional CTSgCTSWhat travelsThe entire object (full source)The entire object (full source)GranularityTransport request levelCommit level (= released TR)Delta?No — full object replacementNo — full object in each commit
In Git terms: the repository stores the complete serialized source of each object at each commit. When you pull a commit into QAS/PRD, the full object is deserialized and overwrites what's there.
This is the same as traditional CTS — when you transport ZCL_SALES_ORDER, the entire class moves, not just the changed method.
Multiple Commits on the Same Object
Scenario: Developer makes 3 bug fixes on ZCL_SALES_ORDER across 3 separate TRs.
Commit 1 (TR DEVK900201): Fix method VALIDATE_ORDER
Commit 2 (TR DEVK900202): Fix method CALCULATE_TAX
Commit 3 (TR DEVK900203): Fix method CHECK_STOCK
What happens when you pull into QAS?

If you pull Commit 3: You get ALL three fixes. Pulling a commit means
you get everything up to and including that commit. The system will have
the state of the object as of Commit 3.
If you pull Commit 2: You get fixes 1 and 2, but NOT fix 3.
You cannot cherry-pick just Commit 2 and skip Commit 1.
Pulls are sequential — you move forward to a point in history.

Traditional CTS comparison:
In traditional CTS, you could theoretically import TR 900202 without 900201
(though this would often cause issues). In gCTS, the sequential nature is
enforced — you always move forward to a specific commit, getting everything
before it.
The Bug Fix Workflow: Step by Step
Timeline:
─────────────────────────────────────────────────────────

1. Bug reported in PRD
│
2. Developer opens ADT → connects to DEV
│
3. Developer modifies ZCL_SALES_ORDER
├── Creates/uses transport request DEVK900201
├── Makes the fix
├── Activates (Ctrl+F3)
├── Tests locally in DEV
│
4. Developer releases TR DEVK900201
│ └── gCTS Observer Job automatically commits + pushes to Git
│
5. In QAS: Basis admin opens gCTS Fiori app
├── Sees new commit for DEVK900201
├── Clicks Pull
├── ZCL_SALES_ORDER is updated in QAS
│
6. QAS testing happens
│
7. In PRD: After approval, admin opens gCTS Fiori app on PRD
├── Pulls the same commit
├── ZCL_SALES_ORDER is updated in PRD
│
8. Bug is fixed in production
Who Does What
ActionWhoWhereToolDevelop & fixDeveloperDEVADT (Eclipse) or SE80Release TRDeveloperDEVADT or SE01Commit to GitAutomaticDEV (Observer Job)BackgroundPull to QASBasis Admin / Release MgrQASgCTS Fiori AppTestQA TesterQASVariousPull to PRDBasis Admin / Release MgrPRDgCTS Fiori App
Using the Fiori App for the Bug Fix
On the QAS system, the admin:

Logs into Fiori Launchpad on QAS
Opens "Git-enabled CTS" app
Selects the repository (e.g., Z_WORKBENCH)
Sees the commit list — the new commit from the developer's released TR is visible
Clicks on the commit → sees which objects are included
Clicks Pull → the commit is pulled, objects are imported
Checks the pull log for success/errors

Same process repeats on PRD after QAS sign-off.

3. DEV STARTING POINT: Developer's Morning Routine
Traditional CTS: What You Did Before

Log into DEV (ADT or SAP GUI)
Find or create your object
Lock it in a transport request
Start coding
No concept of "pulling" — DEV just has whatever was developed there

gCTS: What Changes (and What Doesn't)
The developer does NOT pull in DEV.
This is the most common misconception. Here's why:

DEV is the source of truth — code originates here
The Git repository receives commits FROM DEV
You don't pull into DEV from Git (in the standard flow)
DEV always has the latest state because that's where development happens

Developer's First Action in DEV
It's the same as before:

Open ADT → connect to DEV system
Find your package / object
If creating new: Right-click package → New → [Object Type]
If modifying existing: just open it and start editing
The system prompts for a transport request → create or select one
Code, activate, test
When done: release the TR

There is no "git pull" step in DEV for normal development.
Conflict Scenario: Two Developers, Same Object
Scenario: Developer A and Developer B both need to change ZCL_SALES_ORDER.
In Traditional CTS

Dev A locks the object in TR 900301
Dev B tries to modify → gets a lock error ("Object locked in request DEVK900301 by USER_A")
Dev B must wait, or get Dev A to release, or use a shared TR

In gCTS — It Works the Same Way!
The ABAP lock mechanism hasn't changed. gCTS doesn't add Git-style parallel
editing to the ABAP development experience.

Dev A locks ZCL_SALES_ORDER in their TR
Dev B gets the same lock error
Dev B must wait for Dev A to release

The Git part only kicks in AFTER the TR is released. During active
development, the workflow is identical to traditional CTS.
However, there IS a scenario where gCTS changes things:
Parallel Development with Branches (Advanced)
If your team uses branches (available from S/4HANA 2020):
main branch ─────●─────●─────●──────
\
feature branch ─────●─────●─────

You can create a feature branch in the gCTS Fiori app
DEV system checks out the feature branch
Development happens on that branch
When ready, the branch is merged back to main
QAS/PRD pull from main

But this is an advanced setup. Most teams start with a single main branch,
which makes gCTS feel very similar to traditional CTS.

Quick Reference: Traditional CTS vs gCTS
TopicTraditional CTSgCTSDev creates TRYesYes (unchanged)Dev releases TRQueues for STMS importTriggers Git commitMove to QASSTMS import by adminPull via Fiori appMove to PRDSTMS import by adminPull via Fiori appObject lockingTR-based locksTR-based locks (same)Rollback in QAS/PRDRe-import old TR or manual fixPull an older commitDevelopment toolADT / SE80ADT / SE80 (unchanged)Transport toolSTMS (tcode)gCTS Fiori AppWhere code livesTransport files (.cofiles/.data)Git repositoryVisibilityTransport logsGit commit historyParallel devNot natively supportedBranches (2020+)

The Rollback Advantage (Why gCTS Matters)
This is where gCTS genuinely improves life:
Traditional CTS rollback:

Object broken in QAS after import
You must fix it in DEV, create new TR, release, import again
Or manually revert in QAS (risky, not recommended)

gCTS rollback:

Object broken in QAS after pull
Open gCTS Fiori app on QAS
Find the previous good commit
Pull that commit → system reverts to that state
No need to touch DEV at all for the rollback

This is one of the biggest practical benefits of gCTS.

Summary: What Actually Changes for a Developer
Almost nothing in daily coding. You still:

Use ADT or SE80
Create transport requests
Lock objects in TRs
Activate objects
Release TRs

What changes:

After release, your code goes to Git (automatically)
Moving to QAS/PRD uses the Fiori app "Pull" instead of STMS "Import"
You can see full commit history in the Fiori app
Rollbacks become much easier
Branching is possible (if your team adopts it)

BAPI_SAG_CHANGE Insert Pricing Condition

2026-04-06T09:49:52.564000+02:00

Hi,
I'm trying to insert a new pricing condition to an item of a scheduling agreement (ME32L) with BAPI_SAG_CHANGE, although return message states success condition is not inserted while quantity is updated successfully . How can it be done with this BAPI?
Here is my code:

DATA: lv_agreement_no TYPE bapimepoheader-po_number VALUE 'XXXXXXXXXX', 
      lt_item         TYPE TABLE OF bapimeoutitem,
      lt_itemx        TYPE TABLE OF bapimeoutitemx,
      lt_cond         TYPE TABLE OF BAPIMEOUTCONDITION,
      lt_condx        TYPE TABLE OF BAPIMEOUTCONDITIONX,
      lt_return       TYPE TABLE OF bapiret2.     



APPEND VALUE #( item_no = '00070'
                TARGET_QTY = 5 ) TO lt_item.
APPEND VALUE #( item_no = '00070'
                item_nox = 'X'
                TARGET_QTY = 'X' ) TO lt_itemx.

APPEND VALUE #( item_no    = '00070'
                cond_type  = 'ZD06'      
                cond_unit = 'ST'
                cond_p_unt = 1
                cond_value = '15.50'    
                currency   = 'USD'      
                change_id  = 'I' ) TO lt_cond. 


APPEND VALUE #( item_no    = '00070'
                cond_type  = 'X'
                cond_value = 'X'
                currency   = 'X'
                cond_unit = 'X'
                cond_p_unt = 'X'
                ) TO lt_condx.


CALL FUNCTION 'BAPI_SAG_CHANGE'
  EXPORTING
    purchasingdocument = '3901001961'
  TABLES
    item               = lt_item
    itemx              = lt_itemx
    item_condition     = lt_cond
    item_conditionx    = lt_condx
    return             = lt_return.


IF NOT line_exists( lt_return[ type = 'E' ] ).
  CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = 'X'.

  LOOP AT lt_return INTO DATA(ls_ret).
    WRITE: / ls_ret-type, ls_ret-message.
  ENDLOOP.
ENDIF.

Thank you

Issue Updating IS-Oil Fields (UOM Group & Conversion Group) via FM MATERIAL_UPDATE_ALL

2026-04-06T13:28:35.213000+02:00

Hi Experts,

I am extending a material to multiple plants and need to update IS-Oil specific fields in the material master, namely UOM Group and Conversion Group (IS-Oil view). For this, I am using the function module MATERIAL_UPDATE_ALL. Although the FM executes successfully without any errors and updates standard fields correctly, the IS-Oil fields are not getting updated. The material is extended to the plant properly, required values are passed in the relevant structures, and debugging does not show any explicit error—yet the changes are not reflected in the material master.

Could you please confirm whether MATERIAL_UPDATE_ALL supports updating IS-Oil fields like UOM Group and Conversion Group? Are there any specific structures (e.g., OIB* tables), update indicators, or additional flags required to update these fields? Alternatively, is there any recommended BAPI/FM for maintaining IS-Oil data in the material master? Any guidance would be highly appreciated.

Thanks & Regards,

Neeraj Jain

How to create Follow up cr plant wise in sap mdg by using api

2026-04-07T17:42:07.236000+02:00

Background:
Parent CR: Plants will be added to the cr and the cr will be activated,
then after create follow up cr plant wise.
CR1 For Plant 1: CR1 should contain only plant1 data
CR2 For Plant 2: CR2 should contain only plant 2 data.
I have configure follow up cr as Active for parallel change processing.
I am able to create parallel cr but in both cr I can see data for Plant 1 and Plant2.
I tried deleting the data by using Governance api and change request api.
cr, but unable to do so
Is there any other way to achieve the required functionality?

Choose transport popup - functionality on a custom Fiori Application?

2026-04-07T19:28:49.524000+02:00

Hi all - We have a custom Fiori application that is based on a older legacy program of ours. With clean clore being the goal alot of our source code has been adjusted to use SAP ABAP cloud released objects. The Fiori application has checkboxes for user selection on the UI and when trigerred -> ABAP back-end will add entries to some custom DB tables that we have. Our old legacy program allowed the user to choose a customizing request via a popup to capture these entries in the transport. The idea is to build out the same functionality on our Fiori Application. Prompt user for customizing transport on the UI and then capture the DB entries to the selected transport.

We used the below function modules for the transport functionality in our old legacy program that I believe are no longer clean core compatabile/not released for public cloud. Has anybody had a similar requirement in the past? Does SAP have released cloud objects to replace the older function modules? Doing some research into this at the moment.
CALL FUNCTION 'TRINT_ORDER_CHOICE'
CALL FUNCTION 'TR_OBJECTS_INSERT'

RAP: Issue Calling Standard FM IQS4_ADD_DATA_NOTIFICATION (COMMIT restriction)

2026-04-08T10:54:40.044000+02:00

Hello everyone,

I am currently developing a RAP-based Fiori application and have a requirement to update data from a custom table in the UI to a notification using the standard function module IQS4_ADD_DATA_NOTIFICATION.

I added a custom button on the UI that retrieves data from the selected line and then calls this function module to perform the update. However, based on RAP architecture, function modules or BAPIs that contain explicit COMMIT WORK or ROLLBACK WORK statements are not allowed. When triggering the action, I encounter a BEHAVIOR_ILLEGAL_STATEMENT dump.

I am aware of possible approaches such as using a background job or bgPF (background processing framework). However, I am looking for guidance on the most suitable and recommended solution for this specific scenario

Has anyone faced a similar issue or found a suitable workaround for this scenario in RAP?

I would appreciate any guidance or best practices.

Thank you,

ATC check tool not working - ERT

2026-04-08T11:51:05.424000+02:00

Unable to execute the ATC check due to below error, find the attached for details:-

Result of check run does not exist

The objects passed the chosen checks without any finding

Hi colleagues pls i am relatively new to Workflows in SAP and i have an issue with the binding

2026-04-08T16:37:16.299000+02:00

Specifically i have price approval WF and after decision i want to inform some colleagues via email.T o determine the recipients for this mail i created activity and task with method GETMAILRECIPIENTS within an object in swo1. When i run the method during runtime the lt_rec has three records: ABAP program last line of the method: swc_set_table container 'RECQ' lt_rec. however when i check the container i see: Not set for that step in SWI1. within that method the RECQ is set as export parameter. I created bindings both in the task and (from method RECQ to task RECQ) and also from Step to Workflow. everywhere i have defined RECQ the same way as export multiline wfsyst-agent. can someone help what am i still missing?

Transporting OAuth Scope for v4 OData service /IWFND/V4_ADMIN

2026-04-09T00:38:39.196000+02:00

I have created an OData v4 service binding for my RAP service. I can use transaction /IWFND/V4_ADMIN to publish my service and include it in a customizing request. I create the required OAuth scope. When I use transaction SCC1N to copy my transport to another client my service is published there. This is great because it means that my service will be published in downstream systems when the transport is imported.

My issue is with the OAuth scope. I don't see how to include this in a transport, and when I go to the 2nd client I have to create the OAuth scope again.

What is the correct procedure? Is there a way to transport the OAuth scope, or will I have to create it in all the downstream systems?

I have reviewed SAP Help and can't find an answer to this. Ditto with KBAs like 3304204 & 3605323. Any assistance much appreciated

S/4HANA Private Cloud 2023 FPS03

How to remove a condition and create again?

2026-04-10T11:04:28.375000+02:00

Hi,

We have created a condition and transported to production but somehow it is not visible in P.
Then in a new customizing request we deleted the condition and created again.
But in this case we get an error message and Desicion Table is not visible despite there are Data Access Definitions.
What can be the solution do you have any idea?

Regards.

How to restrict user from changing Business Partner's name in BP using bapi bupa

2026-04-10T11:22:16.663000+02:00

Hi ,
I have to restrict first and last name change of a business partner(customer) in BP transaction when hit save it should check if there are any invoice or order made for that user, If there aren't any orders for the BP then allow the name change and if there is order made for it then restrict it.
Should I use BUPA_FURTHER_CHECKS_IPI this or BUPA_GENERAL_EXPORT or BUPA_API_MODIFY, or is there any other way i can do it, or using some other badi is can do it.

Any suggestions if u have please let me know.
Thanks for the help.

T005K ISO dialling code greater than 4 characters

2026-04-13T02:52:18.496000+02:00

The ISO Dialling Codes for Jersey, Guernsey, and Isle of Man are 44-1534, 44-1481, and 44-1624 respectively. How do I enter these into the T005K - TELEFTO field, given that the TELEFTO has a length of 4 characters

ALRTCATDEF - How to change the error message format from action FM (MDG)

2026-04-13T20:08:14.671000+02:00

Hi,

Kindly help to get the ALRTCATDEF message in proper format.
I have done the ALRTCATDEF setup in my MDG system. In the action FM I am filling my return_tab with error messages.
If return_tab has error messges then AIF alert is triggered and also mail is triggered. The mail is configured in ALRTCATDEF in long/short message text tab. There, I am using container object to fill the message. Container object has message with type bapiret2. I am using that and only specified message filed with multiple lines as continuous text (&messages[].message[]&).

But when I get mail, whole bapiret2 structure also comes in mail.
Example: <msg_type> <msg_class> <msg_num> <message> <msg_v1> <msg_v2> etc.

(E ZMSG_CLS 009 Error in CR Request Error in CR Request)

But expectation is just the <message> since I added only the message field (&messages[].message[]&) like: Error in CR Request.

Did someone encountered such issue or this is just standard and SAP processes all the fields of return_tab?

If not please help me configure it correctly. Please fell free to ask any inputs.

Thanks,
Rahul

ALRTCATDEF - How to change the error message format from action FM (MDG)

2026-04-14T00:16:58.734000+02:00

Hi all,

Kindly help to get the ALRTCATDEF message in proper format.

I have done the ALRTCATDEF setup in my MDG system. In the action FM I am filling my return_tab with error messages.

If return_tab has error messges then AIF alert is triggered and also mail is triggered. The mail is configured in ALRTCATDEF in long/short message text tab. There, I am using container object to fill the message. Container object has message with type bapiret2. I am using that and only specified message filed with multiple lines as continuous text (&messages[].message[]&).

But when I get mail, whole bapiret2 structure also comes in mail.

Example: <msg_type> <msg_class> <msg_num> <message> <msg_v1> <msg_v2> etc.

(E ZMSG_CLS 009 Error in CR Request Error in CR Request)

But expectation is just the <message> since I added only the message field (&messages[].message[]&) like: Error in CR Request.

Did someone encountered such issue or this is just standard and SAP processes all the fields of return_tab?

If not please help me configure it correctly. Please fell free to ask any inputs.

Thanks,

Rahul

"Update is terminated"PM_ORDER_PRINT_CONTROL

2026-04-14T08:22:35.086000+02:00

In Quality system i am able to take print, but in Production throwing dump "SAPLCODB" NOT_FOUND" update termination error.

Missing field in Partners Tab in VA01

2026-04-15T04:30:13.720000+02:00

I am encountering an issue in the Partners tab of VA01. I was trying to make a standard field show up beside the Partner Definition.

I did try to uncheck the Ctry/Reg and Tel no. columns but nothing happens

bapi_po_create1 error

2026-04-15T13:52:21.048000+02:00

hi experts,

please help to solve error while creating bapi_po_create1

code :

TYPES: BEGIN OF ty_DATA,
         bsart TYPE ESART,
         bukrs TYPE BUKRS,
         ekorg TYPE EKORG,
         ekgrp TYPE BKGRP,
         lifnr TYPE LIFNR,
         matnr TYPE MATNR,
         werks TYPE EWERK,
         lgort TYPE LGORT_D,
         menge TYPE BSTMG,
         netpr TYPE BPREI,
         eindt TYPE EINDT,
         waers TYPE WAERS,
       END OF ty_DATA.

DATA : IT_DATA TYPE TABLE OF TY_DATA,
       WA_DATA TYPE TY_DATA.

data : wa_POHEADER  type  BAPIMEPOHEADER,
wa_POHEADERX  type  BAPIMEPOHEADERX,
it_RETURN  type table of  BAPIRET2,
wa_RETURN type  BAPIRET2,
it_POITEM  type table of  BAPIMEPOITEM,
wa_POITEM type BAPIMEPOITEM,
it_POITEMX  type table of BAPIMEPOITEMX,
wa_POITEMX type BAPIMEPOITEMX,
it_POSCHEDULE  type table of  BAPIMEPOSCHEDULE,
wa_POSCHEDULE type  BAPIMEPOSCHEDULE,
it_POSCHEDULEX  type table of BAPIMEPOSCHEDULX,
wa_POSCHEDULEX  type  BAPIMEPOSCHEDULX,
lv_EXPPURCHASEORDER type  BAPIMEPOHEADER-PO_NUMBER.

DATA : IT_FILE TYPE STRING.

PARAMETERS  P_FILE TYPE LOCALFILE.

AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.

  CALL FUNCTION 'F4_FILENAME'
    EXPORTING
      PROGRAM_NAME  = SYST-CPROG
      DYNPRO_NUMBER = SYST-DYNNR
      FIELD_NAME    = ' '
    IMPORTING
      FILE_NAME     = P_FILE.
  .

START-OF-SELECTION.

  IT_FILE  = P_FILE.

  CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      FILENAME                = IT_FILE
*     FILETYPE                = 'ASC'
      HAS_FIELD_SEPARATOR     = 'X'
*     HEADER_LENGTH           = 0
*     READ_BY_LINE            = 'X'
*     DAT_MODE                = ' '
*     CODEPAGE                = ' '
*     IGNORE_CERR             = ABAP_TRUE
*     REPLACEMENT             = '#'
*     CHECK_BOM               = ' '
*     VIRUS_SCAN_PROFILE      =
*     NO_AUTH_CHECK           = ' '
* IMPORTING
*     FILELENGTH              =
*     HEADER                  =
    TABLES
      DATA_TAB                = IT_DATA
* CHANGING
*     ISSCANPERFORMED         = ' '
    EXCEPTIONS
      FILE_OPEN_ERROR         = 1
      FILE_READ_ERROR         = 2
      NO_BATCH                = 3
      GUI_REFUSE_FILETRANSFER = 4
      INVALID_TYPE            = 5
      NO_AUTHORITY            = 6
      UNKNOWN_ERROR           = 7
      BAD_DATA_FORMAT         = 8
      HEADER_NOT_ALLOWED      = 9
      SEPARATOR_NOT_ALLOWED   = 10
      HEADER_TOO_LONG         = 11
      UNKNOWN_DP_ERROR        = 12
      ACCESS_DENIED           = 13
      DP_OUT_OF_MEMORY        = 14
      DISK_FULL               = 15
      DP_TIMEOUT              = 16
      OTHERS                  = 17.
  IF SY-SUBRC <> 0.
* Implement suitable error handling here
  ENDIF.

  LOOP AT it_data INTO wa_data.

    REFRESH: it_poitem, it_poitemx, it_poschedule, it_poschedulex, it_return.
    CLEAR: wa_poheader, wa_poheaderx, lv_exppurchaseorder.

    "HEADER

wa_POHEADER-DOC_TYPE = WA_DATA-BSART.
wa_POHEADER-COMP_CODE = wa_data-bukrs.
wa_POHEADER-PURCH_ORG = WA_DATA-EKORG.
wa_POHEADER-PUR_GROUP = WA_DATA-EKGRP.
wa_POHEADER-VENDOR = WA_DATA-LIFNR.
wa_POHEADER-CURRENCY = WA_DATA-WAERS.

wa_POHEADERX-DOC_TYPE = 'X'.
wa_POHEADERX-COMP_CODE = 'X'.
wa_POHEADERX-PURCH_ORG = 'X'.
wa_POHEADERX-PUR_GROUP = 'X'.
wa_POHEADERX-VENDOR = 'X'.
wa_POHEADERX-CURRENCY = 'X'.

"ITEM

wa_POITEM-MATERIAL = WA_DATA-MATNR.
wa_POITEM-PLANT = WA_DATA-WERKS.
wa_POITEM-STGE_LOC = WA_DATA-LGORT.
wa_POITEM-QUANTITY = WA_DATA-MENGE.
wa_POITEM-NET_PRICE = WA_DATA-NETPR.

APPEND wa_poitem TO it_poitem.

wa_POITEMX-MATERIAL = 'X'.
wa_POITEMX-PLANT = 'X'.
wa_POITEMX-STGE_LOC = 'X'.
wa_POITEMX-QUANTITY = 'X'.
wa_POITEMX-NET_PRICE = 'X'.

APPEND wa_poitemX TO it_poitemX.

" SCHEDULE

wa_POSCHEDULE-DELIVERY_DATE = WA_DATA-EINDT.

APPEND wa_POSCHEDULE TO IT_POSCHEDULE.

.
wa_POSCHEDULEX-DELIVERY_DATE = 'X'.

APPEND wa_POSCHEDULEX TO IT_POSCHEDULEX.

CALL FUNCTION 'BAPI_PO_CREATE1'
  EXPORTING
    POHEADER                     = wa_POHEADER
   POHEADERX                    = wa_POHEADERX
*   POADDRVENDOR                 =
*   TESTRUN                      =
*   MEMORY_UNCOMPLETE            =
*   MEMORY_COMPLETE              =
*   POEXPIMPHEADER               =
*   POEXPIMPHEADERX              =
*   VERSIONS                     =
*   NO_MESSAGING                 =
*   NO_MESSAGE_REQ               =
*   NO_AUTHORITY                 =
*   NO_PRICE_FROM_PO             =
*   PARK_COMPLETE                =
*   PARK_UNCOMPLETE              =
IMPORTING
   EXPPURCHASEORDER             = lv_EXPPURCHASEORDER
*   EXPHEADER                    =
*   EXPPOEXPIMPHEADER            =
TABLES
   RETURN                       = it_RETURN
   POITEM                       = it_POITEM
   POITEMX                      = it_POITEMX
*   POADDRDELIVERY               =
   POSCHEDULE                   = it_POSCHEDULE
   POSCHEDULEX                  = it_POSCHEDULEX
*   POACCOUNT                    =
*   POACCOUNTPROFITSEGMENT       =
*   POACCOUNTX                   =
*   POCONDHEADER                 =
*   POCONDHEADERX                =
*   POCOND                       =
*   POCONDX                      =
*   POLIMITS                     =
*   POCONTRACTLIMITS             =
*   POSERVICES                   =
*   POSRVACCESSVALUES            =
*   POSERVICESTEXT               =
*   EXTENSIONIN                  =
*   EXTENSIONOUT                 =
*   POEXPIMPITEM                 =
*   POEXPIMPITEMX                =
*   POTEXTHEADER                 =
*   POTEXTITEM                   =
*   ALLVERSIONS                  =
*   POPARTNER                    =
*   POCOMPONENTS                 =
*   POCOMPONENTSX                =
*   POSHIPPING                   =
*   POSHIPPINGX                  =
*   POSHIPPINGEXP                =
*   SERIALNUMBER                 =
*   SERIALNUMBERX                =
*   INVPLANHEADER                =
*   INVPLANHEADERX               =
*   INVPLANITEM                  =
*   INVPLANITEMX                 =
          .

READ TABLE it_return INTO wa_return WITH KEY type = 'E'.
  IF sy-subrc = 0.
    WRITE: / 'Error for Vendor:', wa_data-lifnr.
    LOOP AT it_return INTO wa_return.
      WRITE: / wa_return-type, wa_return-message.
    ENDLOOP.
  ELSE.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        wait = 'X'.

    WRITE: / 'PO Created Successfully:',lv_EXPPURCHASEORDER.
  ENDIF.

ENDLOOP.

error :

thankyou.

EWM - Modifying custom fields in HU header using fm /SCWM/HUHDR_ATTR_CHANGE sometimes does not work

2026-04-16T06:27:51.520000+02:00

Hi, EWM/ABAP experts.

Good day!
Need your help for some technical query please.
I need to understand how function module /SCWM/HUHDR_ATTR_CHANGE works.

I need to update an HU during Goods Receipt of an Inbound Delivery via Warehouse Monitor (/SCWM/MON) in an EWM system. The BADI we found for this is /SCWM/IF_EX_DLV_GM_PROCESS, method CHECK_DOCUMENT. We've tested it and it works, we are able to persist data in our custom fields in HU header table.

Now the problem is sometimes it does not work.
In this particular instance, I was trying to post GR to update an HU like normal, but even though we're getting the values correctly, the database is not getting updated at all.

I have a theory that Update Task is the culprit, but I am not very familiar with the Update Task feature of ABAP. This is because when I enabled Update debugging, a debugger session popped out saying that the changes in the FM might be overwritten.

So my main questions are:

How does fm /SCWM/HUHDR_ATTR_CHANGE work? Does it change the HU tables directly, or it's just putting the changes in a buffer?
Can another process like Update Task override changes in HU header maintenance during the same runtime, even without errors?

Thanks for your help!

Purchase Contract Create SOAP API- PurchasingContractERPRequest_In_V1 ( item category D)

2026-04-17T15:38:01.411000+02:00

I am using the SOAP API for Purchase contract to create Service Purchase Contract but getting the error as : "Maintain Services or LImits".Not able to find what all the fields we can pass in order to create purchase contract?

Could anyone please share me the sample payload for this SOAP API.Please find the payload which we are using:

<n0:PurchasingContractERPRequest_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<MessageHeader>
<CreationDateTime>2026-03-21T12:00:00.0000000Z</CreationDateTime>
</MessageHeader>
<PurchasingContract actionCode="01" itemListCompleteTransmissionIndicator="true">
<CompanyID>0100</CompanyID>
<ProcessingTypeCode>WK</ProcessingTypeCode>
<ValidityPeriod>
<StartDate>2026-03-19</StartDate>
<EndDate>2026-06-03</EndDate>
</ValidityPeriod>
<ExchangeRate>
<ExchangeRate>
<UnitCurrency>USD</UnitCurrency>
<QuotedCurrency>USD</QuotedCurrency>
<Rate>1.00000</Rate>
</ExchangeRate>
<ExchangeRateFixedIndicator></ExchangeRateFixedIndicator>
</ExchangeRate>
<TargetAmount currencyCode="USD">999999999.00</TargetAmount>
<SellerParty>
<InternalID>0004100000</InternalID>
</SellerParty>
<ResponsiblePurchasingOrganisationParty>
<InternalID>0001</InternalID>
</ResponsiblePurchasingOrganisationParty>
<ResponsiblePurchasingGroupParty>
<InternalID>001</InternalID>
</ResponsiblePurchasingGroupParty>


<Item actionCode="01">
<ID>00010</ID>
<TypeCode>01</TypeCode>
<ProcessingTypeCode>9</ProcessingTypeCode>
<CancelledIndicator>false</CancelledIndicator>
<BlockedIndicator>false</BlockedIndicator>
<TargetQuantity unitCode="C62">1</TargetQuantity>
<ProductCategory>
<InternalID>01</InternalID>
</ProductCategory>
   <ServiceItemSpecificDetails>
      <AlternateAllowedIndicator>true</AlternateAllowedIndicator>
      <ByBidderProvidedIndicator>true</ByBidderProvidedIndicator>
      <PriceChangeAllowedIndicator>true</PriceChangeAllowedIndicator>
   </ServiceItemSpecificDetails>
<PriceSpecificationElement actionCode="01">
<TypeCode>PB00</TypeCode>
<Rate>
<DecimalValue>200.00</DecimalValue>
<MeasureUnitCode>C62</MeasureUnitCode>
<CurrencyCode>USD</CurrencyCode>
<BaseDecimalValue>1</BaseDecimalValue>
<BaseMeasureUnitCode>C62</BaseMeasureUnitCode>
</Rate>
</PriceSpecificationElement>
<DeliveryTerms>
<QuantityTolerance>
<OverPercentUnlimitedIndicator>true</OverPercentUnlimitedIndicator>
</QuantityTolerance>
</DeliveryTerms>
<Description languageCode="EN">Consulting</Description>
<AccountingCodingBlockDistribution>
<AccountingCodingBlockAssignment>
<AccountingCodingBlockTypeCode>U</AccountingCodingBlockTypeCode>
</AccountingCodingBlockAssignment>
</AccountingCodingBlockDistribution>
<FollowUpGoodsReceiptRequest>
<RequirementCode>1</RequirementCode>
</FollowUpGoodsReceiptRequest>
<FollowUpInvoiceRequest>
<RequirementCode>1</RequirementCode>
</FollowUpInvoiceRequest>
</Item>
</PurchasingContract>
</n0:PurchasingContractERPRequest_V1>