Master data: maintain "Goods Issue Processing Time" in R3 and CIF it ?

Hello,
we want to use the so called GIPRT (Goods Issue Processing Time) in the APO material master (Tab: GR/GI) to schedule SNP PREQs. I can maintain the field in APO but finally I'm looking for maintaining it in the conencted R3 material master (MM02). I see a field in R3 called MARC-GI_PR_TIME but after scanning the material master customizing I think you can't add that to any dynpro in MM01/02/03.
I wonder if this field (MARC-GI_PR_TIME) in R3 is truly meant for maintaining the Goods Issue Processing Time in R3 and transfering it to SCM via the CIF or whether its there but has no function or is maintained somewhere else in R3. Any idea ?
Workaround obviously would be to maintain the field in APO directly - but that's what I want to avoid since 99% of master data are coming from R3.
Regards
Thomas

Hi Thomas,
You can implement user exit EXIT_SAPLCMAT_001 and can write code based on your requirement ( May be you want to transfer this GR time for some of the products only). You can push the values by this user exit for any field in APO.
Thanks,
Abhilasha

Similar Messages

Regarding Goods Reversal & Goods Issue Process for PO

Hi Experts,
           Could you any one tel me what is Goods Reversal and Goods Issue process for PO...
How to create the FM & detailed Procedure Pls?....
Please any one tel me.......
Thanks & Reagards
HB

Hi Hans,
SOURCE : HELP.SAP
Purpose
Inventory Management uses this process in such a way that the goods issue posting is divided into two parts that run in separate systems. Posting the GI document in the supplying plant results in a message to the receiving plant. The receiving plant then performs a complementary posting. The physical goods receipt takes place as usual.
Prerequisites
When using batch processing, the following prerequisites must be fulfilled:
Both the original and target systems have the same batch definition level.
The batch definition level is either the material or the client.
An ALE scenario exists for materials and classes (characteristics).
Unique batch numbers exist cross-system.
Batches can only be changed in their original system when they are not decoupled. From an organizational point of view, this must also lead to the batch status being changeable in a local SAP R/3 system. For example, this is impossible when transfer posting to a new batch and results in further actions, for example, relabeling containers, palettes and so on.
Characteristics
As for the purchase order in a one-system situation, the system should automatically post the material into the stock in transit at the receiving profit center and the corresponding Profit Center Accounting using intra-CC transfer prices at goods issue for the purchase order and the unchecked delivery. This requirement is valid for one-system situations as well as for two-system situations where there is an ALE interface. No internal billing document should be created.
In a two-system case, the receiving profit center should be derived at goods issue from the unchecked delivery. Profit Center Accounting then takes place with
Stock change transfer price to stock
Internal expense to internal sales
Internal clearing account to stock change transfer price.
Account determination in a purchase order for an intra-company-code transaction must be different from account determination in external transactions. Automatic GR/IR account clearing is required in both one-system and two-system situations.
The stock in transit must be visible in the receiving profit center.
The system must send a shipping notification at goods issue in one-system and two-system situations.
You need to create an invoice document for the internal and external trading statistics for cross-boundary deliveries as well as for customs purposes.
GR/GI slips are created.
Process Flow
Goods Issue Posting for Stock Transfers
The delivery triggers the goods issue in the issuing system.
The call contains the stock transport order data known in the delivery, including the PO item and the logical system of the recipient.
The transaction (quantity and value updates) is selected using the movement type:
Movement Type
Function
641
Goods issue with UB logic (Creation of stock in transit at recipient, immediate value posting).
647
As 641, however the goods receipt line (movement type 101) is added automatically, so that the goods receipt is posted at the same time as the goods issue (one-step procedure).
You determine the movement type according to the schedule line category in Sales and Distribution. The goods issue for a cross-system stock transfer must be different from the integrated transaction. This is achieved by adding a new movement type.
You post quantities and values at goods issue in the same way as a goods issue for a sales order. That is to say, the quantity is posted in the supplying plant and the value is adjusted to that of the stock account. The offsetting posting is made to a clearing account. The known data from the delivery is copied to Accounting to balance the account where necessary.
The system creates a message to the appropriate receiving system for all items with reference to a cross-system purchase order. The system does not perform any validity checks on the recipients data before posting begins. Incorrect Customizing results in the update being terminated.
If a goods issue has receiving plants in different logical systems, an IDoc is sent for each system.
In order that the goods receipt is able to use the values on the receiver side, you must add the values used to post the goods movement, in particular the transfer prices, to the IDoc.
The logic for recognizing the profit center switch functions as follows: At goods issue, the system recognizes that the profit center of the issuing plant is different from the profit center of the receiving plant. The system derives the profit center node from the relevant profit center.
Data Transfer
The IDocs sent by the issuing plant trigger the goods issue postings in the receiving plant.
Background Posting in the Receiving System
The goods receipt is posted in the receiving system using the IDoc. The interface receives the data from the goods issue in the supplying plant. The following processes now run at the recipient:
The system finds the update control for the GR part of the posting.
The goods movement is posted with the new movement type.
During valuation of the goods receipt, the system might, where necessary (UB logic), refer to the values (legal value and the value from the parallel valuation type, if you are using the transfer price function) from the IDoc.
The PO history is updated. The PO history is updated with the material document number from the second part of the GI posting. The GI document number is not stored in the supplying plant, because there is no way to display this document.
In two-step procedures the goods receipt is posted to the stock in transit.
Reversal
You can only reverse this goods issue for the PO using the cancellation transaction in SD. You cannot reverse the GI in Inventory Management.
The material document that is automatically created in the receiving system cannot be canceled. This reversal is triggered by the sending system (the actual reversal of the GI document takes place there) and transmits the data, including the reversal movement type, to the receiving system. No actual reversal is posted in the receiving system, because the material document number of the original document does not exist in this system. This scenario is applicable for cases where you use the two-step procedure (with stock in transit).
Distribution of Batch Master Data and Characteristics
The batch information is transported using the message category BATMAS.
When you create a cross-system goods issue, the system creates the corresponding IDoc using the message category BATMAS.
When the delivery arrives in the target system, the batch and all the information is already present in the system.
Changes to the batch data are also distributed using the message category BATMAS.
The batch can be decoupled in the receiving SAP R/3 system. This means that the batch can have a different status in the receiving system than in the original system. By setting an indicator at material level, you decide whether the batch can be decoupled or whether the batch and all its attributes are copied from the original system. "Decoupled" i.e. "locally independent" batches are no longer distributed from its own system.
The batch data does not need to be available before the physical goods receipt takes place. The goods receipt into the stock in transit does not usually refer to the batch unless you are working with batches with assigned active ingredient values.
If the GI cannot be posted for organizational reasons, for example because the goods cannot be loaded onto a truck until 10pm, then you can post the goods into the GR blocked stock. This stock is also non-batch-specific.
In cases where the GI IDoc arrives before the batch IDoc, then the GI IDoc can be subsequently posted by a periodically scheduled report (transaction BD87). A program like this exists in the SAP standard system. In Customizing for MM Inventory Management (activity Copy, Change Movement Types), you should make settings to define that manual creation of batches at goods receipt is not allowed.
Shipping Notification
The shipping notification is required in the receiving system due to its relevance for MRP. In this way, for example, a change in delivery date determined at goods issue is sent to the receiving system using the shipping notification. The shipping notification can also be used when posting the GR batches.
Reward if found helpfull,
Cheers,
Chaitanya.

Goods Receipt Processing Time in Days field

Hi,
what does "Goods Receipt Processing Time in Days" in material master affect ?
Regards

Dear SAPBUG,
Goods Receipt Processing time
in-house produced materials, 1 day GR - after completion of production of Huge lot size then they see Whole lot is
Made as per Requirment or not. so this takes time 1 day. so this time will get effected in Scheduling. MRP takes into
account this 1 day & schedules the dates accordingly
For Purchase materials, 1 day GR - same applies after purchasing concern persons will check the material is as per
requirment or not. MRp schedules as per days given in this field
in simple words SAP has given Flexbile option
Regards
Madhu

How to design Master datas?? Whats is Time Scenarios???Explain..

How to design Master datas?? Whats is Time Scenarios???
Can anybody explain about Time Scenarios???

Hi..
to tell it is huge ..
but a slice of it
Design Create design documents
Prod. Make the product
Quality Confirm quality of product
Sales - Market the product
Purchase Procure the items
Accounts To control the cost of Mfg
These steps should be understood as a general approach. To what extent they must be carried out depends
on the actual situation and the experience of the project members involved.
After deciding on the business process being dealt with, the basic steps to implementing a BI based solution
are:
1. Focus on the structure of information
Develop a complete understanding of the underlying business processes. Create an Entity Relationship
Model (ERM) of the business process
The ERM as a function of the information
2. Focus on analytical needs - Overcome model complexity
Create a valid data model. Translate the ERM to the Multi-Dimensional Model (MDM) / Star schema
The MDM as a function of the analytical processing
3. Build the solution as a part of an integrated data warehouse
The Star schema on the BI stage are the InfoCubes. Translate the MDM / Star schema to one or more
InfoCube.
coming to time ..
How real-world changes are dealt with, i.e. how the different time aspects are handled is the most
important topic with data warehouses.
The attributes of a characteristic that will reside in its master data table are determined in the modeling
phase. Each attribute can be defined individually as being time dependent:
There is one time dependent check box for each attribute in the attribute tab page section.
Time dependency of an attribute allows you to keep track on the changes over time of the relation of the
characteristic and the time dependent attribute values.
In terms of technical implementation, two master data tables exist if we have both non-time dependent
and time dependent attributes.
One master data table stores all relations to non-time dependent attributes (name of the table:
/BIC/P<InfoObject name>) and
One table stores relations to time dependent attributes (name of the table: /BIC/Q<InfoObject
name>).
The time dependent attributes master data table has additional DATETO and DATEFROM system
attributes. In queries the different constellations are addressed using the key date ( Query properties).
The validity attributes are not available for navigation.
The text table, or better the description attributes, may be defined as time dependent.
SID tables with respect to master data:
The SID table is always generated if an InfoObject is not defined as attribute only (tab page general).
This table is used if the access to an Infocube or DataStore Object uses a navigational attribute or if the
access is via a characteristic without attributes. Name of the table: /BIC/S<InfoObject name>
The non-time dependent attribute SID table of a characteristic for access via non-time dependent
attributes. Name of the table: /BIC/X<InfoObject name>
The time dependent attribute SID table of a characteristic for access via time dependent attributes.
Name of the table: /BIC/Y<InfoObject name>
with regards,
hari kv

Override consignment price determination during goods issue process

Hi ALL,
My requirement is that User is asking want to override consignment price determination during
goods issue process. Is there any BADI/User Exit or Enhancement spot which can override the price value and in the
database level during Goods issue.
If yes provide me the enhancement details and where I can implement.
I will very thankful to you all if I get your valuable input.
Regards
Subhasis

Dear Laxman,
Check these links,
https://wiki.sdn.sap.com/wiki/display/ERPLO/Batch+Determination
Automatic batch determination
Re: how to make the batch determination process automatic
Regards
Mangalraj.S

How to find unassigned master data text objects in process chain in bi

Hi
Please let me know how to find the unassigned master data text objects in process chain.

hi,
actually if u want to find that , is ur Unassigned Infoobject in present in process chain or not, , that u can find out just by right
click on your DTP (master data Txt datasource--> Master data text ), if this is present in Process chain, then on ryt click, the process chain option will be active. by clicking over that u can find the name in which this exists.
thanks.

Goods Issue Posting Time

hi all
how to get the Goods Issue Posting Time for the purchase order.
thanks
bala

Hi
If i understood correctly, you are looking to track the issues pertaining to PO.
There is no relevancy of issues of PO, if the material procured is stock material. This means, your procurement is intended for stock only. Issues will be made to the departments who approachs with necessary requirement.
If your procurement is for consumption (account assigned PO), your GR document is nothing but the consumption doc. You can find the goods consumption time from the GR document.
warm regards
sairam akundi

Steps for master data loading by using process chain

Hi
I want to load the Master data by using the process chain . Can anyone tell me the step-by-step method for loading the master data .
I means what are the processes should i need to include in the process chain . Pls tell me in sequenece .
i ll assing the points
kumar

Hi,
The process os loading master data is similar to transaction data in terms of using the infopackages.
First you have to load Attr followed by texts and hierarchy.For master data you have to include the process type called as Attribute change run.This can be included as a separate process type or using the AND process.
Hope this helps.
Assign points if useful.
Regards,
Venkat

Master data loading by using process chain

hi
I want to load the master data by using the process chain in BI7.0 . How can i do this one .
Can anyone tell me the step-by-step method for loading the master data.
kumar

Hi Kumar,
check this link to load the master data by using the process chain
Re: Process Chain : Master Data
cheers
Sunil

Lightroom 5 slowdown, my post processing times have tripled and the develop tasks take multiple seconds for one adjustment, Please Help. . . .

my post processing times have tripeled and the develop tasks take multiple seconds for one adjustment, Please Help. . . .

my post processing times have tripeled and the develop tasks take multiple seconds for one adjustment, Please Help. . . .

"Check BW Master Data" in MC62 issue

Hello,
I am creating CVCs from an Info provider. I am selecting the "Check BW master data" when i create CVCs immediately.
When i intentionally put wrong values in characteristics which are not in RSA1 (Info object-->Maintain Master data) i am unable to create the CVC when i create a single CVC.
But when i create CVC immediately from Cube (The cube is uploaded from a data source through flat file) with values in flat files which are not in RSA1 (Info object-->Maintain Master data) , the system is not complaining that there is no master data. It is creating CVC for what ever values i have in Flat files. Is this normal or is the system supposed to error out just like it did when i create a Single CVC?
Any idea how i can tackle this. Appreciate your help in advance.
Thanks.
Sai.

Hi Sai,
I can share what I understand.
CVC is not BW data, it's part of APO DP master data and has connections to BW in the sense that you use the characteristics which are defined in BW.
When you are creating CVC and checking for BW master data, you are checking if characteristic data is correct BW wise also.
If the master data for characteristic is not found, BW is issuing an error.
On the other hand, data in Cube is already a BW data, and all the BW related checks are already done at the time when your data has come from flat file to the Cube. So, there is no chance that you would get BW check related error when you create CVC from cube.
Hope this helps.
Thanks - Pawan

I have a question about error messange in [Post Goods Issue] process.

Dear all.
I'm working a SD system operater in south Korea.
I'm really sad for our recent defeat in worldcup gameTT.
Anyway, I need your help.
When I make outbound delivery document and post GI,
I got a message like this :
Fld selectn for mvmt type 601 / acct 43010101 differs for Customer goods movement (015)
Message no. M7093
I don't know to solve this problem.
I Think this is a kind of LE module's error,
But there are no LE professional in my company.
So, I need your help.
And also, I try to find this error using message class M7, no 093.
I found the message in the class, but embarrassly, there is no result the maessage's where-used-list!.
PLZ let me know the solution about this.
Best Regards.
Kwangkyun choi.
Edited by: Kwang-Kyun Choi on Jun 21, 2010 3:16 AM
Edited by: Kwang-Kyun Choi on Jun 21, 2010 3:22 AM

Hi,
If you read the long text of the error message, you can find out that the cause of the problem is due to the incompatible setting of fields selection between movement type and G/L account.
SAP note 9281 will help you to solve this problem.
The system is functioning as designed, a check is done on both tables T004F (FI) and T156B (MM). These tables define what data is required, optional,etc... when processing the transaction. There are certain fields that are contained on both tables.
For those fields that are redundant, the field selections must be the same. Since the data is processed through a single dynpro, the system must have only one instruction for a data field. This is why message M7 093 is being generated when optional is specified for MM and required is specified for the General Ledger.
Please read SAP note 9281 and, according to it, execute the report RM07CUFA to compare the field selection definitions in MM
and FI. Maintain the incorrect settings from the report (when a red line appears, it means that it is wrong so you have to review your customizing settings). The customizing transactions for setting the field status are:
- OMBW -> field status group by movement type.
- OBC4 -> field status group for finantial documents, defined in the G/L account master data.

Master Data attributes failed in Process chain

Hi All,
Master data load has failed at vendor attributes DELTA load, and error message is "'Update mode R is not supported by the extraction API".
Actually in the last PC delta run it was failed at same vendor attributes delta run, due to special characters, we allowed those special characters in RSKC transaction and technically made PSA red request to RED after that In order to Run the PC, We selected that Red request in PSA (Which has the records) and updated with Scheduler. PC ran well after that.
and today PC got failed at same place showing he message as "'Update mode R is not supported by the extraction API".
There are no red requests in data source (Info course), and No delta's missed.
Can anyone please let us know the why it is happening ? (solution is we can re-init it or got options to run it) but we are looking for why this issue is happening ?
All inputs are much appreciated.
Thanks in advance,
Teena

Hi Teena,
You get this type of error when the data source does not support repeat of delta
or
init flag might have corrupted some times so that it wont allow the delta load to run.
it happens because the DS does not support R or Repeat of delta.
For more information on Update mode:
Go to SE12, write data type as "RODMUPDMOD". Read the documentation given there.
You can try multiple options to resolve this.
Simply set the QM status of the last failed delta to GREEN and reload your master data with Full Repair. Your deltas will follow.
the best way for this situation would be to re-init.
Regards
Kp

Deleting Master Data Requests in a Process Chain

Hi All,
I need to delete and reload master data in a process chain. I created an ABAP program that uses the function module "RSDMD_DEL_MASTER_DATA" to delete the master data. I invoke this program from my process chain, and this is working well. My master data is being deleted nicely.
Question, however. I noticed that this does not delete the actual data request for that InfoObject. If I manage that attribute, I still see the request appearing, eventhough I see no records when I select the option to maintain master data.
Can anyone tell me how I can delete the requests for master data, and how this can be done through a process chain?
Your assistance would be greatly appreciated.
Thank you,
John Stabile

Hi John,
I created a program giving the name of the master data object. Using this object, I found the request entries from rsiccont
Then I check these found entries in rsbkrequest, so as to find the status is successful.
rsbkrequest-tstate eq '2'.
rsbkrequest-ustate eq '2'
see the total code below.. you can copy paste the same
*TABLES
tables: rsiccont.
*SELECTION SCREEN
selection-screen begin of block a01 with frame title text-t01.
select-options : s_icube for rsiccont-icube obligatory.
parameter: p_num type i obligatory.
parameter: p_test as checkbox.
selection-screen end of block a01.
*Internal Table Definition
types: begin of t_rsiccont.
        include structure rsiccont.
types: recno like sy-tabix,
       end of t_rsiccont.
data: i_rsiccont type standard table of t_rsiccont with header line,
       i_rsiccont_ok type standard table of t_rsiccont with header line,
       i_rsbkrequest type standard table of rsbkrequest with header line.
*Work areas
data: wa_rsiccont type t_rsiccont.
*Variables
data: lv_rnr   type rsiccont-rnr.
*AT SELECTION SCREEN
at selection-screen on s_icube.
select single rnr
    into lv_rnr
    from rsiccont
    where icube in s_icube.
if sy-subrc ne 0.
    message 'InfoCube not found' type 'E'.
endif.
*START-OF-SELECTION
start-of-selection.
select * up to p_num rows
    into table i_rsiccont
    from rsiccont
    where icube in s_icube.
if sy-subrc eq 0.
    select *
      into table i_rsbkrequest
      from rsbkrequest
      for all entries in i_rsiccont
      where requid eq i_rsiccont-rnsidlast.
   if sy-subrc eq 0.
      loop at i_rsiccont.
        read table i_rsbkrequest with key requid = i_rsiccont-rnsidlast.
*check if status is = 2.
        check sy-subrc eq 0.
        check i_rsbkrequest-tstate eq '2'.
        check i_rsbkrequest-ustate eq '2'.
*actual mode -> delete the recrod!
        if p_test is initial.
          call function 'RSSM_PROCESS_REQUDEL_MDT'
            exporting
              i_dta     = i_rsiccont-icube
              i_request = i_rsiccont-rnr.
        endif.
        append i_rsiccont to i_rsiccont_ok.
      endloop.
    endif.
endif.
*display list of all request numbers deleted!
write: 'List of delete request numbers'.
uline.
skip.
loop at i_rsiccont_ok.
    write: i_rsiccont_ok-rnr.
    skip.
endloop.
=====================================================
You may need to correct the formatting
Edited by: Shailesh Khandarkar on Nov 11, 2009 7:42 AM
Edited by: Shailesh Khandarkar on Nov 11, 2009 7:46 AM

Regarding Goods Reversal and Goods Issue process for Production orders

Hi,
I have a issue regarding Goods Reversal and Goods Issue process for Production orders.
Actually I am having a Z - Function Module in that i am passing production order number other details to
make the Goods Reversal happen.
The code for the above is as below:
 i_mvtit-material = wa_mdfa-matnr.
 i_mvtit-plant = i_resb-werks.
 i_mvtit-spec_stock = 'Q'. "New
 i_mvtit-stge_loc = 'ZWIP'.
 i_mvtit-stge_type = i_resb-lgtyp. "New
 i_mvtit-batch = i_resb-charg. "New
 i_mvtit-orderid = i_resb-aufnr.
 i_mvtit-spec_stock = i_resb-sobkz.
 i_mvtit-entry_qnt = i_resb-enmng.
 i_mvtit-entry_uom = i_resb-erfme.
 i_mvtit-entry_uom_iso = i_resb-meins. "New
 i_mvtit-wbs_elem = v_frwbs.
 i_mvtit-move_type = '262'.
 i_mvtit-xstob = 'X'.
 i_mvtit-gr_rcpt = i_resb-aufnr. "New
 i_mvtit-reserv_no = i_resb-rsnum.
 i_mvtit-res_item = i_resb-rspos.
 APPEND i_mvtit.
* HEADER ELEMENTS
 k_gmvt_code-gm_code = '03'.
 k_gmvt_head-pstng_date = sy-datum.
 k_gmvt_head-doc_date = sy-datum.
* CREATE GOODS MOVEMENTS
 CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
 EXPORTING
 goodsmvt_header = k_gmvt_head
 goodsmvt_code = k_gmvt_code
 TABLES
 goodsmvt_item = i_mvtit
 return = i_return.
The Above code does the Goods Reversal but then i will update one Z Table with fields like
Production Order Number[AUFNR], Number of Reservation[RSNUM], Item Number of Reservation [RSPOS], Material Number [MATNR], Requirement Quantity [BDMNG], WBS element[PSPNR] etc. If Above BAPI runs sucessfully.
That is happening correctly.
But Then actual issue is i have do Goods Issue for those Z-Table records.
There i will give Production order Number's & Storage Location in Selection-Criteria.
Then i need to do Goods Issue for that order.
The code i had written as follows.
* POPULATE VALUES FOR BAPI CALL
 i_mvtit-material = i_zpsi7603_01-matnr.
 i_mvtit-plant = i_resb-werks.
 i_mvtit-spec_stock = 'Q'. "New
 i_mvtit-stge_loc = p_sloc.
 i_mvtit-stge_type = i_resb-lgtyp. "New
 i_mvtit-batch = i_resb-charg.
 i_mvtit-orderid = i_resb-aufnr.
 i_mvtit-spec_stock = i_resb-sobkz.
 i_mvtit-entry_qnt = i_resb-enmng.
 i_mvtit-entry_uom = i_resb-erfme.
 i_mvtit-entry_uom_iso = i_resb-meins. "New
 i_mvtit-wbs_elem = v_frwbs.
 i_mvtit-move_type = c_261.
 i_mvtit-mvt_ind = 'F'. "New
 i_mvtit-xstob = c_x.
 i_mvtit-gr_rcpt = i_resb-aufnr. "New
 i_mvtit-reserv_no = i_resb-rsnum.
 i_mvtit-res_item = i_resb-rspos.
 APPEND i_mvtit.
* HEADER ELEMENTS
 k_gmvt_code-gm_code = c_03.
 k_gmvt_head-pstng_date = sy-datum.
 k_gmvt_head-doc_date = sy-datum.
* CREATE GOODS MOVEMENTS
 CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
 EXPORTING
 goodsmvt_header = k_gmvt_head
 goodsmvt_code = k_gmvt_code
 TABLES
 goodsmvt_item = i_mvtit
 return = i_return.
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 wait = c_x.
 READ TABLE i_return INDEX 1.
 IF i_return-type EQ c_s.
 DELETE FROM zpsi7603_01 WHERE aufnr = i_resb-aufnr AND
 rsnum = i_resb-rsnum AND
 rspos = i_resb-rspos.
 ENDIF.
If i run above code for Goods Issue it is giving error can anybody tell me what changes i need to do to make it work.
The Error Message i am getting is as below:
Qty and / or "delivery completed" ind. or final issue ind. are missing
Error Number for the above is : 264.
Can anybody solve my issue.
Any help will be appreciated.
Thanks in advance.
Thanks & Regards,
Rayeez.

Hi,
Thanks boss.
It is working now correctly.
The issue is the i_mvtit-XSTOB should be equal space in case of Goods issue while incase of Reversal it should be equal to X.
Thanks for ur efforts.
I had awarded you points.
Thanks a lot.
Thanks & Regards,
Rayeez.

Master data: maintain "Goods Issue Processing Time" in R3 and CIF it ?

Similar Messages

Maybe you are looking for