1
votes

I have a requirement from the customer that involves presenting information in transaction VA42 (contracts) that are saved in a number of custom tables. The data is not avaliable via an append structure on VBAK and I'm not able to make this change myself.

I've registered the screen 8309 and started to add my fields to it. As such, I've created a PBO module in order to have a place to map the data to the fields in the screen. I've placed a breakpoint in the module, it's being triggered and the data I want to present is being retreived. Nothing I've done so far though writes it to the field in the user exit.

What I've tried:

  • I gave the fields a 'parameter id' so I can use GET and SET PARAMETER ID. This doesn't work, the fields remain empty after using this statement.

http://hastebin.com/qinerexola.sql

  • I gave the fields a normal name instead of naming the field on the structure/name and tried with DYNP_VALUES_UPDATE to map the data to the supplied field. Sy-subrc returns 0 but the field isn't updated.

http://hastebin.com/anakirikah.sql

  • I gave the fields a name of (structure)-(field) and tried using the above function module. This also didn't work.
  • I looped at screen and saw the name of my field come by but this structure has no information on it's value, or at least that I can see.

I don't have the option to append fields to the VBAK, is it still possible to populate the fields of extended screens with custom data from customer tables?

1
Welcome to SO! Are you declaring FIELD contract-req_ref. (or FIELD ZSD_VA_ADD_FIELDS-REF_REGEX., whichever it is in your case) before making the call to the module? This introduces the field value into scope so that you may read and write to it within the module.gkubed
Your hastebins are empty. Paste the code here.Suncatcher
For the field to show the value it needs to also be maintained as a global field in the main program, in your case SAPMV45A. From the description you give of the problem and what you have tried it is not clear if this is the case, the source of you module would help. You can create the variable in MV45ATZZ.Gert Beukema
@gkubed, the FIELD statement has no effect in PBO.Gert Beukema
@GertBeukema Oops! Thanks, I was thinking PAI.gkubed

1 Answers

0
votes

For the field to show the value it needs to also be maintained as a global variable in the main program, in your case SAPMV45A. From the description you give of the problem and what you have tried it is not clear if this is the case, the source of your module would help. You can create the variable in MV45ATZZ.