Authorization of movement types

Dear All,
I want to restrict users for Movement type, Material type wise.
As per requirement ROH materials will pass through the 103,105 (quality check cycle) during procurement.
For HIBE material quality check (103,105) is not required. GRN will be done through 101.
Problem is - The same person is to be authorize for the above scenarios.
With u201CM_MSEG_BWE -Goods Receipt for Purchase Order: Movement Type objectu201D we can authorize user for particular movement type. But how to do this for the above case.
Please suggest,
Regards,
Vijay P.Bhaware

Hi,
You can make the quality managenet view active for the material for which you want to do quality check, maitain this field in material master for ROH material , and dont make this field for other materials select the check box post to quality inspection in the QM view in material master, then you can do all GR with movment type 101, but the materials for which you have maintain QM view will get post to quality stock.
regards,
zafar

Similar Messages

Restricting Authorization for movement types for Storage Location

Hi Xperts
I have a requirement that 313 & 315 material movements should not have any BBD/SLED check.However , 314 & 316 should have BBD/SLED check.
Suppose there are two storage locations : A(Good Stock) & B(Blocked Stock).
I want one User-ID should be authorized to perform 313 & 315 from A to B.However the same USER-ID should not be authorized to perform 313 & 315 from B to A.They should be authorized only to perform 314 & 316 from B to A.
All the above trasnactions will be performed either via MIGO or via MB1B.
How to achieve this.Pls suggest.
Regards,
Soumick

Hi Soumick,
You can try by creating 2 roles as given below.
Role A - Tcode Migo
BWART - 313 and 315
for object M_MSEG_LGO field LGORT - give only A
Role B - Tcode Migo
BWART - 314 and 316
for object M_MSEG_LGO field LGORT - give only B
Try assigning both the roles to user and see... Not 100% sure...but u can try out.... You need to have such scenarios tested very thoroughly.
With Regards
Nishad Showkath

Movement type 161 Migo

Hello, I was trying to receive a material using trx MIGO. (movement type 101). The system did not allow to make the movement, and show me a message saying that: User without authorization to movement type 161( Return for PO order).
I want to know because the system had that behavior.
Thanks in advance for the help
Regards
Enzo

Hi Enzo,
I think too you may have a return order and that defaults a 161 movement.
If that is what you want to receive, then ask the user with the authorization problem to run SU53 transaction after getting the error message and pass that screen to your BASIS/ Authorization guy to add the required authorizations to your users.
If that is not what you want to receive, your buyers need to change the PO and take out the return indicator.
Hope this helps.
Monica Araoz.

BASIS--to restrict authorization for a PO document type & 122 movement type

Dear All,
Plz guide me how to restrict authorization for a PO document type & for a movement type 122 i.e. for eg. if a user has authorization for PO document type IC then he should not be able to rum movement type 122 for any T-code he runs.
Thanks in advance
Arpit
Basis

Hi,
Your request was not too clear to me.. As per my unde
Here is some details of Authorization object related to Purchase Order:
Document Type in Purchase Order( M_BEST_BSA )
Purchasing Group in Purchase Order (M_BEST_EKG )
Purchasing Organization in Purchase Order (M_BEST_EKO)
Plant in Purchase Order (M_BEST_WRK )
Document Type in Outline Agreement (M_RAHM_BSA )
Purchasing Group in Outline Agreement (M_RAHM_EKG )
Purchasing Organization in Outline Agreement ( M_RAHM_EKO )
Plant in Outline Agreement ( M_RAHM_WRK )
This can be helpfull to you to restrict authorization to PO..
In Organization Level, it can be restricted by Purchasing group, Purchasing organization and plant..
Regards,
Sandip

No authorization for this transaction with movement type 601

Dear All,
This is chandra i am getting this error in delivery level " No authorization for this transaction with movement type 601. If give the authorization for SAP ALL its working fine. If give the authorization for SAP SD T.Codes i am getting this error. Plz help me.
Thanks and regards
Chandra

Dear Chandra,
Check with -
T. Code: OMJJ
Select Movement Type: 601 and Double-Click: "Allowed Transaction" (From Left-hand side) .
Check whether the Transaction is allowed for Movement Type 601 or not
Note: if Transaction is not listed (i.e. not allowed) and you wanna allow this Transaction with Movement type 601, then -
Up-there, Tab: New Entry. Click on it.
Maintain entry as:
MovTy: 601
TCode: As reqd.
and Save.
Best Regards,
Amit

Authorization Object Related To Movement Type

Hi,
I meet one problem, one user want to check which user can use MB1A t-code with movement type 201 and 202, but I know there are some authorization object related to movement type and I want to use suim with mb1a t-code and authorization object to check the user, but I don't know the authorization object about movement type in MB1A t-code, does anyone can help?

Go to SU24, enter the transaction code and press execute.
Here you can see the all authorization object whose are used for the transaction code MB1C.
Regards
Dev

Authorization object for 351 movement type

Dear expert
Please guide me
How to restrict 351 movement type for created STO for self plant in self plant?
for eg : there are 2 plant 1001, 2001.
STO CREATED IN 1001 PLANT
IN THIS suppling plant : 2001 & Recieving plant : 1001
Now, suppling plant has to do 351 movement type & Recieving plant has to do 101 movement type.
Now my doubt is receving plant should not do 351 movement type.
but it shows that my 1001 plant (receving plant) doing 351 MOVEMENT TYP.
Logically it should not do this.
So , How to restrict 351 movement type for created STO for self plant in self plant?
Regards
SANTOSH KADAM.

M_MSEG_BMB
M_MSEG_BWA
M_MSEG_BWE
M_MSEG_BWF
M_MSEG_LGO
M_MSEG_WMB
M_MSEG_WWA
M_MSEG_WWE
M_MSEG_WWF
if your 1001 plant never needs a 351 movement, then dont assign the 351 together with 1001 in these objects for roles that are used in 1001 plant.
But if 1001 needs to perform as well a 351 to any other plant, then you cannot use authorization to restirct it.

Authorization check for posting a specified movement type on certain plant

<h5>Iu2019m posting goods movements using BAPI_GOODSMVT_CREATE, I have to check If the user has authorities for posting for a specified movement type on certain plant.
How do I implement it, do I need to create a authorization object with ACTVT, WERKS and BWART, what will be value of ACTVT in this case?
Or is there any other way through which the BAPI can automatically check for authorization.</h5>

Just to bring to your notice that authorization check is done by the BAPI. Please check the function module.
AUTHORITY-CHECK OBJECT 'M_MSEG_WMB'
              ID 'ACTVT' FIELD '03'
              ID 'WERKS' FIELD I_MSEG-WERKS.
     AUTHORITY-CHECK OBJECT 'M_MSEG_BMB'
              ID 'ACTVT' FIELD '03'
              ID 'BWART' FIELD I_MSEG-BWART.
Regards,
Lalit MOhan Gupta

No authorization for this transaction with movement type

Hi gurus,
My sd consultant is authorized to execute VLO2N Tcode. But it is giving the error as follows
"No authorization for this transaction(vlo2n) with movement type 643" ...
When i try to do the same thing through BASIS ,it gives no error..
Thanks in Advance,
Vaibhav Gore.

Hi Vaibhav,
T. Code PFCG --> Give particular Role Name then click Change Button -->
Then Click Autherization Button --> then Click Change Autherisation(pencil)
Go and Click or Drill down the Material Management : Inventry Management
1.This is --> Goods Movement : Storage Location Type :
Click --> Movement type (Inventry Management) Press F4 --> u can choose ur valid type
Like --> 623 GI iss:cust.ret.pack
Regards
kesav

Movement type: Authorization checking procedure

Hello,
I want to check the Users with 321/322 movements types, I know that authorization object is M_MSEG_BWE but I donot know how to check.
Our basis person is off, Please suggest how to check and pathways.
regards,
JPS

>
S K wrote:
> The best way to get this is Search for the roles in SUIM ---> Roles by Complex Selection Criteria -
> Selection by Field name . Put Filed name BWART values 321/322. This will list down the roles with the given values and then check who are the users with these roles..
Out of interest, why do you want to choose roles & then get users from the assignment when running it against the user? Don't forget that the OP doesn't have much experience in this.

BDC for MIGO for GR OutBound Delivery( A01 & R05 ) from Movement Type 107 to 109

Hi,
I am stuck with a very typical situation need all your expertise and advices for a solution.
We are basically trying to create change the movement type from 107 to 109 through MIGO.
I have made a BDC recording for MIGO ( because we would like to track each delivery specifically under shipment , I know that there is a BAPI which is there to do this but it works fine if we do the shipment with Purchase Order as input which dont want in that manner )
Process:
1. Creating Production Order
2. Creating Purchase Order
3. Creating STO
4. Deliveries
5. PGI for Deliveries
6. Shipment for group of outbound Deliveries
I have created a z program where i am passing shipment number in the selection screen.
Then it would take all the deliveries for that shipment and pass each delivery to MIGO and process it and change the status from 107 to 109.
Interesting part here is, the code works absolutely perfect only from my ID. But when I test from other ID it is not executing, so to check where is the problem I have added mess_tab to the CALL TRANSACTION to capture what message is been populated for my ID comparing with others
Message Captured on Others ID's:
MSGID: 00
MSGNR: 344
MSGV1: SAPLMIGO
MSGV2: 1300
Message Captured on MY ID:
MSGID: MIGO
MSGNR: 012
MSGV1: 5000005802
MSGV2: (empty)
This is the problem this program is executing only on MY ID, rest all ID's it is not processing.
We have cross verified with security and basis regarding any authorization issues but nothing came up.
Please help me what could be the issue ( WHY it is processing successfully for my and WHY NOT for other ID's)
Below is the main code :
CALL FUNCTION 'CONVERT_DATE_TO_EXTERNAL'                     " Converting Date format to DD/MM/YYYY
     EXPORTING
       DATE_INTERNAL            = sy-datum
     IMPORTING
       DATE_EXTERNAL            = lv_date_external
     EXCEPTIONS
       DATE_INTERNAL_IS_INVALID = 1
       OTHERS                   = 2.
       IF SY-SUBRC <> 0.                                     "#EC NEEDED
* Implement suitable error handling here
       ENDIF.
*   Validating input shipment number with database table VTTP
       SELECT VTTP~TKNUM
              VTTP~TPNUM
              VTTP~VBELN
         FROM VTTP INNER JOIN VTTK
         ON VTTP~TKNUM = VTTK~TKNUM
         INTO TABLE IT_VTTP
         WHERE VTTK~TKNUM = P_TKNUM
           AND VTTK~STDIS = 'X'.
       IF sy-subrc = 0.
*   Validating all deliveries having same Delivery type or not
         SELECT * FROM likp INTO TABLE it_likp FOR ALL ENTRIES IN it_vttp WHERE vbeln = it_vttp-vbeln
                                                                            AND vbtyp = 'J'.
         IF sy-subrc = 0.
           CLEAR lv_lines.
           LOOP AT it_likp INTO wa_likp.
             REFRESH:it_vbfa,BDCDATA.
*   Validating if Delivery Type = 109 (GR already done), or Delivery Type = 107 (must process for GR )
             SELECT * FROM vbfa INTO TABLE it_vbfa WHERE vbelv = wa_likp-vbeln
*                                                AND vbtyp_v = 'J'
                                                     AND bwart = '109'.
             IF sy-subrc = 0.
               lv_flag1 = 'X'.
             ELSE.
               SELECT * FROM vbfa INTO TABLE it_vbfa WHERE vbelv = wa_likp-vbeln
*                                                  AND vbtyp_v = 'J'
                                                       AND bwart = '107'.
               IF sy-subrc NE 0.
                 MESSAGE 'No Deliveries with Movement Type "107" ' TYPE 'I'.
               ELSE.
                 lv_flag2 = 'X'.
                 lv_lines = lv_lines + 1.
** BDC for MIGO
                 perform bdc_dynpro      using 'SAPLMIGO' '0001'.
                 perform bdc_field       using 'BDC_OKCODE'
                                               '=OK_GO'.
                 perform bdc_field       using 'GODYNPRO-ACTION'
                                               'A01'.
                 perform bdc_field       using 'GODYNPRO-REFDOC'
                                               'R05'.
                 perform bdc_field       using 'GODEFAULT_TV-BWART'
                                               '109'.
                 perform bdc_field       using 'BDC_CURSOR'
                                               'GODYNPRO-OUTBOUND_DELIVERY'.
                 perform bdc_field       using 'GODYNPRO-OUTBOUND_DELIVERY'
                                               wa_likp-vbeln. "'80019574'.
                 perform bdc_field       using 'GOHEAD-BLDAT'
                                               lv_date_external. "'04/29/2015'.
                 perform bdc_field       using 'GOHEAD-BUDAT'
                                               lv_date_external. "'04/29/2015'.
                 perform bdc_field       using 'GOHEAD-WEVER'
                                               '1'.
                 perform bdc_dynpro      using 'SAPLMIGO' '0001'.
                 perform bdc_field       using 'BDC_OKCODE'
                                               '=OK_POST1'.
                 perform bdc_field       using 'GODEFAULT_TV-BWART'
                                               '109'.
                 perform bdc_field       using 'GOHEAD-BLDAT'
                                               lv_date_external. "'04/29/2015'.
                 perform bdc_field       using 'GOHEAD-LFSNR'
                                               wa_likp-vbeln. "'0080019574'.
                 perform bdc_field       using 'GOHEAD-BUDAT'
                                               lv_date_external. "'04/29/2015'.
                 perform bdc_field       using 'GOHEAD-WEVER'
                                               '1'.
                 perform bdc_field       using 'GODYNPRO-DETAIL_ZEILE'
                                               '   1'.
                 perform bdc_field       using 'GOITEM-ERFME'
                                               'EA'.
                 perform bdc_field       using 'GOITEM-ERFMG'
                                               '1'.
                 perform bdc_field       using 'GOITEM-LSMNG'
                                               '1'.
                 perform bdc_field       using 'GOITEM-LSMEH'
                                               'EA'.
                 perform bdc_field       using 'GOITEM-MIGO_ELIKZ'
                                               '1'.
                 perform bdc_field       using 'GOITEM-BWART'
                                               '109'.
                 perform bdc_field       using 'GOITEM-LGOBE'
                                               'RX Cross-docking'.
                 perform bdc_field       using 'BDC_CURSOR'
                                               'GODYNPRO-DETAIL_TAKE'.
                 perform bdc_field       using 'GODYNPRO-DETAIL_TAKE'
                                               'X'.
                 PERFORM bdc_dynpro      USING 'SAPLMIGO' '1300'.
                 PERFORM bdc_field       USING 'BDC_CURSOR'
                                               'G_TIP_DONT_SHOW_AGAIN'.
                 PERFORM bdc_field       USING 'BDC_OKCODE'
                                               '=OK_TIP_GO'.
                 PERFORM bdc_field       USING 'G_TIP_DONT_SHOW_AGAIN'
                                               'X'.
*& Avoid unncessary screens to populate while processing background.
                 LV_OPTIONS-DISMODE = 'N'.
                 LV_OPTIONS-UPDMODE = 'S'.
                 LV_OPTIONS-NOBINPT = 'X'.
                 CALL TRANSACTION 'MIGO' USING BDCDATA OPTIONS FROM LV_OPTIONS MESSAGES INTO IT_MESSTAB1 .
                 WAIT UP TO 1 SECONDS.
                 DELETE IT_MESSTAB1 WHERE MSGTYP NE 'E'.
                 IF IT_MESSTAB1[] IS NOT INITIAL.
                   APPEND LINES OF IT_MESSTAB1 TO IT_MESSTAB.
                 ENDIF.
               ENDIF.
             ENDIF.
           ENDLOOP.
         ENDIF.
       ELSE.
         MESSAGE 'Shipment Number does not exists Or not Planned' TYPE 'E'.
       ENDIF.
     ELSE.
       MESSAGE 'Please insert Shipment Number' TYPE 'E'.
     ENDIF.
     IF lv_flag1 = 'X' AND lv_flag2 = 'X'.
       MESSAGE 'This shipment is processed with an inconsistent goods receipt' TYPE 'I'.
     ELSEIF lv_flag1 = 'X'.
       MESSAGE 'Shipment already been processed for these deliveries' TYPE 'I'.
     ELSEIF lv_flag2 = 'X'.
       lv_lines1 = lv_lines.
       CONDENSE lv_lines1 NO-GAPS .
       CONCATENATE lv_lines1 'Goods Receipt are posted for the shipment '
              INTO lv_message SEPARATED BY space.
       MESSAGE lv_message TYPE 'I'.
     ENDIF.
* Display Messages from Message TAB.
     DELETE ADJACENT DUPLICATES FROM IT_MESSTAB.
     DATA:lv_msg TYPE string.
     LOOP AT IT_MESSTAB INTO WA_MESSTAB.
       CALL FUNCTION 'FORMAT_MESSAGE'
         EXPORTING
           ID        = WA_MESSTAB-MSGID
           NO        = WA_MESSTAB-MSGNR
           V1        = WA_MESSTAB-MSGV1
           V2        = WA_MESSTAB-MSGV2
           V3        = WA_MESSTAB-MSGV3
           V4        = WA_MESSTAB-MSGV4
         IMPORTING
           MSG       = lv_msg
         EXCEPTIONS
           NOT_FOUND = 1
           OTHERS    = 2.
       IF sy-subrc <> 0.
* Implement suitable error handling here
       ENDIF.
       WRITE:/ lv_msg.
     ENDLOOP.
*        Start new screen                                              *
   FORM BDC_DYNPRO USING PROGRAM DYNPRO.                 "#EC PF_NO_TYPE
     CLEAR BDCDATA.
     BDCDATA-PROGRAM = PROGRAM.
     BDCDATA-DYNPRO   = DYNPRO.
     BDCDATA-DYNBEGIN = 'X'.
     APPEND BDCDATA.
   ENDFORM.
*        Insert field                                                  *
   FORM BDC_FIELD USING FNAM FVAL.                       "#EC PF_NO_TYPE
     CLEAR BDCDATA.
     BDCDATA-FNAM = FNAM.
     BDCDATA-FVAL = FVAL.
     APPEND BDCDATA.
   ENDFORM.
Thanks,
Srini

Hi Rob,
Thanks for quick reply.
I have checked the NOTE : 304122
But there in the NOTE it says ( " BAPI, BAPI_GOODSMVT_CANCEL, BAPI_GOODSMVT_CREATE, CNTL_ERROR" )
These BAPI's work perfectly for (purchase order as input type), but here out type is ( A01 & R05 ) we are giving DELIVERY NUMBER as input to MIGO.
So for this scenario we cannot use those BAPI's mentioned in the NOTE.
Also as stated earlier in the message interesting part is
"The code works absolutely perfect only from my ID. But when I test from other ID it is not executing. Code is working exactly as expected ONLY to my ID. When i try to execute the same code from another's ID it is not working"
So what do you think might be the issue?

Special stock indicator O to add existing custom movement types

Hi Gurus,
Business having the two custom movement types for which they want to add special stock indicator O.
please let me know is it possible to add special stock indicator O to existing movement types.
or
Is it possible to achieve this with creation of new movement types along with current special stock indicators.
Thanks in advance.

have you ever created a new movement type?
try it.
it can only be done by copy of a SAP given movement type, hence it has basically the same functionality as the original movement.
the main purpose for new movement types are to post to other accounts and to segregate authorization.
In other words you cannot add O to an existing movement, you need to create a new movement by copy from a movement that allows this O

Can i restrict a movement type with respect to storage location

Hi
Is there any way to restrict the movement type for a particular storage locations.
For eg.
If am using a Mvt 311 tP btwn storagelocations.
If there are 10 Stlocs in my plant i want to restrict 311 only for 7Slocs.
Is it possible
Guide me
Sunil

Sunil
Please contact your BASIS security team , with the help of Authorization roles you can restrict
Reward if helpful
Regards
venu gopal

Restriction on movement type,storage location on USER ID

Dear Guru's,
I have to restrict movement type 311 on some storage location for some user ID.Following is already done but not able to restrict the movement of material on other storage location rather than defined:
1) Maintained authorization objet M_MSEG_LGO with two storage location ST01,ST02 and movement type 311.
2) Using BADI MB_MIGO_BADI and maintained Z table with USERID,Mvt type 311,storage location ST01,ST02.
Still we are able to do Mvt 311 on other that defined locations in authorization objet M_MSEG_LGO and Z table....
Kindly give ur valuable suggestion to resolve the issue......
With Regards.

HI
For your requirement only I have suggested to create multiple role. In one Role you specify SLOC & MOvt type(only 311) in auth object M_MSEG_LGO & M_MSEG_BWE for slocs where you want 311 movt. In other Roles of goods movt you also specify other SLOCs & all other movt except 311. I mean in the other Role you cant keep the movt type as * in auth object M_MSEG_BWE.
So its a combination of SLOC & MVT tye. Try & give feedback
Shakti
Edited by: SHAKTI BEHERA on Jan 14, 2012 12:15 PM

Restrictions of movement types in MIGO

Hello,
When I select goods receipt in MIGO, I would like the system to avoid using 201 movement type. I mean, if I select goods receipt, it should only work for goods receipt
Is there a way that I can block other movement types like this?
I tried to do it from
SPRO->MATERIALS MANAGEMENT -> INVENTORY MANAGEMENT AND PHYSICAL INVENTORY ->SETTINGS FROM ENJOY TRANSACTIONS -> SETTINGS FOR TRANSACTIONS AND REFERENCE DOCUMENTS
and tried to put some restrictions, but it did not work.
Thanks in advance for your help
Irem

Hi
Access to mvt types can be restricted through authorizations. Check with your basis person (auth object is M_MSEG_BWA).
If you want to skip a particular transaction in MIGO then deactivate it in IMG - MM - Inventory management & phy inventory - Settings for Enjoy Transactions - Settings for Goods Movements (MIGO) - Settings for Transactions and Reference Documents. Select the transaction MIGO - click transaction/event (you can deactivate goods issue here or) - Click goods issue - deactivate which ever are not required. You cannot see deactivated options here in MIGO.
Thanks

Authorization of movement types

Similar Messages

Maybe you are looking for