‎2005 Jan 25 10:22 AM
Dear Team,
I have a query in MIGO : customer changes.
I am trying to add two customer specific fields in MIGO.
main program SAPLMIGO screen number 0310.
I presume the first step is to add these 2 fields in
append structure CI_COBL .
Can some of you guide me regarding available user exits / BADI
and also screen modifications which are necessary.
Special thanks for your precious help,
Aby Jacob ..
‎2005 Jan 27 11:33 AM
Hi Aby,
Have you gone through the below documentation. I think it's useful.
R/3 System account assignment transactions use subscreens, which contain
the various account assignment fields. When generating the screens for
these transactions, the system searches for the most suitable subscreen,
that is, the one containing the most required fields.
If there is no subscreen that contains all the necessary fields, you
have to enter the additional fields in a separate dialog box.
You can define your own subscreens in this step. This means you can
structure your subscreens to suit your own requirements and thus avoid
having to enter account assignment fields in an additional dialog box.
Note
Any changes you make apply in all clients and for all transactions that
use the coding block.
Requirements
To be able to maintain subscreens, you must have authorization to
maintain cross-client tables (S_TABU_CLI).
Defining subscreens
To define a subscreen, proceed as follows:
1. On the Maintain Coding Block Subscreens: Overview screen, select the
Create function.
The system displays the Maintain Coding Block Subscreens: Detail
screen.
2. Enter a 4-character number and a description for your subscreen.
The numbers 9000 to 9999 are reserved for customer subscreens. The
system proposes the next available number from this interval. You
can overwrite the proposed value, if required.
3. Enter a number between 1 and 9 in the Priority field (1 = highest; 9
= lowest).
The priority allows you to "fine tune" the search for the most
suitable subscreen.
4. Maintain the Active indicator.
When looking for suitable subscreens, the system only takes into
account those which are both active and generated.
Note
This function allows you to deactivate both your own subscreens and
the standard SAP subscreens if you do not want to use them.
5. Select the Fields you want to use in your subscreen.
You select a field by assigning a valid position on the subscreen.
Each subscreen can accommodate a maximum of 10 fields. The positions
are numbered from 1 (1st line left) to 10 (5th line right). In
several posting transactions (->) larger subscreens with a maximum
of 40 fields are possible, but these subscreens are not selected
during most transactions.
In certain fields you can display master data texts for the field
values. To do this, select the "With text" field. An entire row is
necessary for this field.
Example
Let us assume you have defined your subscreen as follows:
Field Name Position With text
Asset 1
Order 3 X
Cost center 2
Material 5
Plant 6
In this subscreen the account assignment fields would be displayed
as follows:
Asset Cost center
Order Short descrip. of order
Material Plant
6. When you have finished maintaining your subscreen, you have to save
it. Subscreens are saved in two steps:
a) You store the subscreen in the system using the Save function.
The subscreen is, however, latent.
Subscreens which are not yet effective are flagged as "Not
generated" in the overview list.
b) You activate the subscreen throughout the system using the
Generate function.
Note
If you have no further use for one of your own subscreens, you can
either delete it from the list, or deactivate it using the Active
indicator. The latter method has the advantage that you can regenerate
the subscreen later and use it again.
Maintaining SAP subscreens
The changes you can make to the SAP subscreens delivered in the standard
system are very limited:
o You can deactivate them.
o You can change the priority (see priority).
Note
If you try to delete an SAP subscreen, the system deletes only the
changes you made and restores the standard delivery version.
Reset to standard
Using this function, you can restore all the subscreens to the standard
delivery version. Your changes are not lost, however:
o Any SAP subscreens you changed are reset to standard and flagged in
the overview as "Not currently generated".
o Your own subscreens are flagged as "Not generated".
Generate all
Using this function, you can generate all subscreens
Activities
1. Check whether the standard SAP subscreens meet all your
requirements.
2. Create new subscreens if necessary.
3. If necessary, change the priority or the active indicator for the
preset subscreens.
Please award points if this helps.
Madhavan
‎2005 Jan 25 10:38 AM
Hi Aby,
If you want to fill/check additional account assignment fields you can use enhancement ACCOBL01.
Regards,
John.
‎2005 Jan 25 12:30 PM
Hi John,
Thanks for the immediate response.
Can you provide me some more details.
Step-by-step guide would be a Terrific Help.
Warm regards,
Aby
‎2005 Jan 25 12:40 PM
Hi Aby,
Before I can give any further help I first have to make sure what your requirements are: do you really need to include fields on screen 0310 or do you want to include fields for the account assignment?
Regards,
John.
‎2005 Jan 27 10:40 AM
Hi John,
Sorry for the late reply, I was on leave for 2 days.
I tried modifying sub-screen 340 of SAPLMIGO
with 2 new custom defined fields "ZZBONDNUMBER"
and "ZZBONDREFERENCE".
(these were added in "CI_COBL" structure first.
Can you help me with the IMG link so that these
2 new fields are being displayed as "INPUT" fields
on sub-screen 340 of SAPLMIGO.
Many Thanks,
Aby Jacob
‎2005 Jan 27 11:33 AM
Hi Aby,
Have you gone through the below documentation. I think it's useful.
R/3 System account assignment transactions use subscreens, which contain
the various account assignment fields. When generating the screens for
these transactions, the system searches for the most suitable subscreen,
that is, the one containing the most required fields.
If there is no subscreen that contains all the necessary fields, you
have to enter the additional fields in a separate dialog box.
You can define your own subscreens in this step. This means you can
structure your subscreens to suit your own requirements and thus avoid
having to enter account assignment fields in an additional dialog box.
Note
Any changes you make apply in all clients and for all transactions that
use the coding block.
Requirements
To be able to maintain subscreens, you must have authorization to
maintain cross-client tables (S_TABU_CLI).
Defining subscreens
To define a subscreen, proceed as follows:
1. On the Maintain Coding Block Subscreens: Overview screen, select the
Create function.
The system displays the Maintain Coding Block Subscreens: Detail
screen.
2. Enter a 4-character number and a description for your subscreen.
The numbers 9000 to 9999 are reserved for customer subscreens. The
system proposes the next available number from this interval. You
can overwrite the proposed value, if required.
3. Enter a number between 1 and 9 in the Priority field (1 = highest; 9
= lowest).
The priority allows you to "fine tune" the search for the most
suitable subscreen.
4. Maintain the Active indicator.
When looking for suitable subscreens, the system only takes into
account those which are both active and generated.
Note
This function allows you to deactivate both your own subscreens and
the standard SAP subscreens if you do not want to use them.
5. Select the Fields you want to use in your subscreen.
You select a field by assigning a valid position on the subscreen.
Each subscreen can accommodate a maximum of 10 fields. The positions
are numbered from 1 (1st line left) to 10 (5th line right). In
several posting transactions (->) larger subscreens with a maximum
of 40 fields are possible, but these subscreens are not selected
during most transactions.
In certain fields you can display master data texts for the field
values. To do this, select the "With text" field. An entire row is
necessary for this field.
Example
Let us assume you have defined your subscreen as follows:
Field Name Position With text
Asset 1
Order 3 X
Cost center 2
Material 5
Plant 6
In this subscreen the account assignment fields would be displayed
as follows:
Asset Cost center
Order Short descrip. of order
Material Plant
6. When you have finished maintaining your subscreen, you have to save
it. Subscreens are saved in two steps:
a) You store the subscreen in the system using the Save function.
The subscreen is, however, latent.
Subscreens which are not yet effective are flagged as "Not
generated" in the overview list.
b) You activate the subscreen throughout the system using the
Generate function.
Note
If you have no further use for one of your own subscreens, you can
either delete it from the list, or deactivate it using the Active
indicator. The latter method has the advantage that you can regenerate
the subscreen later and use it again.
Maintaining SAP subscreens
The changes you can make to the SAP subscreens delivered in the standard
system are very limited:
o You can deactivate them.
o You can change the priority (see priority).
Note
If you try to delete an SAP subscreen, the system deletes only the
changes you made and restores the standard delivery version.
Reset to standard
Using this function, you can restore all the subscreens to the standard
delivery version. Your changes are not lost, however:
o Any SAP subscreens you changed are reset to standard and flagged in
the overview as "Not currently generated".
o Your own subscreens are flagged as "Not generated".
Generate all
Using this function, you can generate all subscreens
Activities
1. Check whether the standard SAP subscreens meet all your
requirements.
2. Create new subscreens if necessary.
3. If necessary, change the priority or the active indicator for the
preset subscreens.
Please award points if this helps.
Madhavan
‎2005 Jan 27 11:50 AM
Dear Madhavan,
Many, many Thanks,
This documentation
on "Defining subscreens" was really Good !
Warm Regards,
Aby Jacob ...
‎2006 Oct 05 3:02 PM
Well guys I am very well familar up to the point described in above documentatio. But my question is how a Transaction can guess about that which screen should be called.
e.g I have made a subscreen in Maintain Subscreen for Coding Block. Now how can I guess which transaction will call this sucscreen.
As a ABAPER I think there would some user exit or enhancement through which we call these subscreens for a particular Transaction.
Pls give a detailed answer, I have created a subscreen but dont know how to link it with a particular T-Code. Thnx