Hello Vimal,
This is just the warning and occurs wherein you have not selected members for the above Dimension while executing the Data manager Package. Hence while executing package it selects all the base members where you have not given any selection.
Regards
Bhagyesh Ravange
Hi Nainesh,
Are you able to resolve your SLM system from solution manager ? Please confirm.
Also please follow SAP Note 722514 - Reasons for SAP-RC=223
Regards,
Gaurav
You have two function modules to read these tables:
1. CHANGEDOCUMENT_READ_HEADERS (For reading entries in CDHDR table)
2. CHANGEDOCUMENT_READ_POSITIONS (For reading entries in CDPOS table)
hii Vikash
do as follows
call function 'F4_FILENAME'
exporting
program_name = syst-cprog
dynpro_number = syst-dynnr
importing
file_name = p_file.
lv_fname = p_file.
endform. " BROWSE_FILE
start-of-selection.
call function 'GUI_UPLOAD'
exporting
filename = lv_fname
filetype = 'ASC'
* HAS_FIELD_SEPARATOR = ' '
* 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_barcode.
* 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.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
Hi Jitendra,
Please let me know if assistance is still required.
Regards,
Moshe
Hi Vikash,
To search 'GUI_UPLOAD' in SCN, many threads refer this.
regards,
Archer
I would try to bind the calculated value to a decimal field without any patterns. If it wouldn't help - then it's time for testing 
Some options for you to check and test:
1) check the value in qtotal (e.g. show it in a messagebox)
2) try to bind qtotal to any other decimal field - maybe it's just a "bad" field and you just need to recreate it. I've seen an unexplainable behaviour of fields a couple of times.
3) and - by the way - does the field has enough width for the calculated value? If the value would overlap the cell you can get format surprises from the field.
If it still wouldn't help, then I'd like to have a look at the form.
Hi Sathish,
As per your attached file, uncomment the DAR01-04 Columns from the final internal table.
those should be a separate fields and while arranging the information in final table you have to pass the data in these fields based on your fields conditions.
Regards.
Praveer.
hi,
Can u plz provide any screen shot..............
Where the value of other deduction is appearing with negative indicator in result table itself then try to find out where it is getting calculated and in the schema accordingly you can modify it then place it in deduction window as well.
else go to PE51 Cumulation ID doube click on deductions find out wage type 2009 change the MS as "-" then check the payslip.
Regards
Venkatesh
Check with technical consultant he helps you out to sort out the issue.
Regards
Venkatesh
You didn't read what i asked. i asked for second screen shot from you initial question where you enter user id as CAROL ?
It won't work.
If it is the current record, we can reverse the payroll, and can delete the record from 01 Infotype.
Based on your logic consult with the technical consultant and they will put the logic in suystem by using this exit.
Regards,
Sankarsan
Hi,
Did you happen to find a solution for the subject?
I'm encountering the exact same problem.
Thanks,
Meytal
Hi,
check the pb.ini file used by powerbulder looking in the registry key:
HKEY_CURRENT_USER\Software\Sybase\PowerBuilder\12.5\InitPath
and use a tool like procmon to see if there is a problem when PB open the file.
I don't have pb 12.5 installed, but pb 12.6, in my case, uses the pb.ini located in
C:\Users\<myusername>\AppData\Local\Sybase\PowerBuilder 12.6
Regards
Alberto
Hi Rupesh,
Thanks for your reply. I am using below path to delete assignment.
SAP Menu --> Advanced Planning & Optimization ---> Master Data ----> Application-Specific Master Data ----> Service Parts Planning ----> Bill of Distribution -----> Maintain and display bill of distribution.
As I am new to SPP, can you please tell me how to change validity?
Hi Arijit, I Agree! The assumption for above thesis is there are 2 different systems (System A and System B). A is the legacy and B is new SAP system.The legacy system A could be SAP itself (probably with older version of SAP on different server) or any other different system. It becomes imperative to follow above steps when you are migrating to altogether a new different system. You should close all the transactions in A and should freeze the stock taking statements so that no new material movement or any GL posting is made in system A. Before any new transaction is made in system B, the initial situation at B should be same as that of A. And for this initial stock loading is done. Many more other transactions also like vendor and customer balances are considered here. So this would be wider outlook of entire cut-over activities in that way!
But what about if it is the same system, the same server and the same plant? Do we need to upload the stock again even though it is already present?
My understanding (if I read the original posting)_SAP (System B) is already implemented and PP module is in use. System Adoes not exist anymore. They would have certainly carried out mega cut-over when B went Live. So now the stocks are being built by GR against production order itself in B. If there exists an order of 100 PC against which 30 are already delivered (in B), these should be present in unrestricted use. Do we need to upload stock of 30 PC again here using 563? I think Mahesh's concern is about what would happen if he activates QM at this stage in the same system where MM and PP are already in use. My further query is do we really need to short close existing production order before activating 04 inspection type in to existing system and why?
Anand
hi ,
Did you Run the "MAINTAIN SOURCE FIELDS" step which is third step in LSMW ?
i dont see source fields in the screenshot you put
please confirm
thanks
santosh
Hi,
Condition 4: B=-B i.e. if B is negative Condition 4 must be outermost in the nested if. If its priority is highest. I understood is correct then the solution given by @SUV 123 can be modified as below;
CKF1 = A>B * NOERR (NODIV ( ( A/B ) ) ) * 30
CKF2 = A<B * NOERR ( NODIV( ( ( A- B-B1)/B2 * 30 + 60) ) )
CKF3 = A=B * NOERR (NODIV( (A/B)))* 30
CKF4 - B<0 * 0 + B>0 * CKF1+CKF2+CKF3
Hope this gives you desired solution.
Regards,
Sucheta