Hi,
Create program ZRM07MLBD from RM07MLBD.
Find the internal table G_T_TOTALS_FLAT in program ZRM07MLBD.
Before Display the output (ALV) export the itab to memory.
Arivazhagan S
Hi,
Create program ZRM07MLBD from RM07MLBD.
Find the internal table G_T_TOTALS_FLAT in program ZRM07MLBD.
Before Display the output (ALV) export the itab to memory.
Arivazhagan S
REPORT ZBASICPAY_CONTROL.
TYPE-POOLS SLIS.
TABLES:PERNR,RP50G,Q0008.
INFOTYPES:0008.
SELECTION-SCREEN:BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-000.
PARAMETERS:P_FILE TYPE RLGRAP-FILENAME.
SELECTION-SCREEN:END OF BLOCK B1.
TYPES:BEGIN OF TY_PA30,
PERNR(30) TYPE C,
BEGDA(10) TYPE C,
ENDDA(10) TYPE C,
TRFAR(2) TYPE C,
TRFGB(2) TYPE C,
TRFGR(5) TYPE C,
LGART(5) TYPE C,
BETRG(6) TYPE C,
ANZHL(5) TYPE C,
END OF TY_PA30.
DATA: WA_PA30 TYPE TY_PA30,
IT_PA30 TYPE TABLE OF TY_PA30.
DATA:WA_BDCDATA TYPE BDCDATA,
IT_BDCDATA TYPE TABLE OF BDCDATA.
DATA:WA_BDCMSGCOLL TYPE BDCMSGCOLL,
IT_BDCMSGCOLL TYPE TABLE OF BDCMSGCOLL.
DATA: N(2) TYPE N,
CNT(2) TYPE N,
FLD(20) TYPE C,
X(2) TYPE N,
COUNT TYPE I.
DATA: V_MSG TYPE STRING.
TYPES:BEGIN OF TY_ERROR,
RECORDS TYPE I,
MESSAGE(100) TYPE C,
END OF TY_ERROR.
DATA:WA_ERROR TYPE TY_ERROR,
IT_ERROR TYPE TABLE OF TY_ERROR.
DATA:WA_FCAT TYPE SLIS_FIELDCAT_ALV,
IT_FCAT TYPE SLIS_T_FIELDCAT_ALV.
DATA:BEGIN OF WA_LGART,
LGA01(5) TYPE C,
END OF WA_LGART.
DATA:BEGIN OF WA_BETRG,
BET01(6) TYPE C,
END OF WA_BETRG.
DATA:BEGIN OF WA_ANZHL,
ANZ01(5) TYPE C,
END OF WA_ANZHL.
DATA:IT_LGART LIKE TABLE OF WA_LGART,
IT_BETRG LIKE TABLE OF WA_BETRG,
IT_ANZHL LIKE TABLE OF WA_ANZHL.
DATA: FNAM TYPE STRING.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
PERFORM OPEN_FILE.
START-OF-SELECTION.
PERFORM UPLOAD_DATA.
PERFORM PROCESS_DATA.
PERFORM DISPLAY_ERRORS.
*&---------------------------------------------------------------------*
*& Form OPEN_FILE
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*---------------------------------------------------------------------- *
FORM OPEN_FILE .
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
CHANGING
FILE_NAME = P_FILE.
ENDFORM. " OPEN_FILE
*&---------------------------------------------------------------------*
*& Form UPLOAD_DATA
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM UPLOAD_DATA .
FNAM = P_FILE.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
FILENAME = FNAM
HAS_FIELD_SEPARATOR = 'X'
TABLES
DATA_TAB = IT_PA30.
ENDFORM. " UPLOAD_DATA
*&---------------------------------------------------------------------*
*& Form PROCESS_DATA
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM PROCESS_DATA .
LOOP AT IT_PA30 INTO WA_PA30.
REFRESH :IT_BDCDATA,IT_LGART,IT_BETRG,IT_ANZHL.
SPLIT:WA_PA30-LGART AT ',' INTO TABLE IT_LGART,
WA_PA30-BETRG AT ',' INTO TABLE IT_BETRG,
WA_PA30-ANZHL AT ',' INTO TABLE IT_ANZHL.
perform bdc_dynpro using 'SAPMP50A' '1000'.
perform bdc_field using 'BDC_OKCODE' '=INS'.
perform bdc_field using 'RP50G-PERNR' WA_PA30-PERNR.
perform bdc_field using 'RP50G-TIMR6' 'X'.
perform bdc_field using 'BDC_CURSOR' 'RP50G-CHOIC'.
perform bdc_field using 'RP50G-CHOIC' '0008'.
perform bdc_dynpro using 'MP000800' '2000'.
perform bdc_field using 'BDC_OKCODE' 'UPD'.
perform bdc_field using 'P0008-BEGDA' WA_PA30-BEGDA.
perform bdc_field using 'P0008-ENDDA' WA_PA30-ENDDA.
perform bdc_field using 'P0008-TRFAR' WA_PA30-TRFAR.
perform bdc_field using 'P0008-TRFGB' WA_PA30-TRFGB.
perform bdc_field using 'P0008-TRFGR' WA_PA30-TRFGR.
perform bdc_field using 'P0008-ANCUR' 'EUR'.
perform bdc_field using 'Q0008-IBBEG' '14.11.2014'.
perform bdc_field using 'P0008-WAERS' 'EUR'.
LOOP AT IT_LGART INTO WA_LGART.
N = N + 1.
ENDLOOP.
CNT = 01.
X = 01.
perform bdc_dynpro using 'MP000800' '2000'.
DO N TIMES.
IF CNT > 5.
CNT = 01.
perform bdc_field using 'BDC_CURSOR' 'Q0008-LGART(01)'.
perform bdc_field using 'BDC_OKCODE' '=P+'.
perform bdc_dynpro using 'MP000800' '2000'.
perform bdc_field using 'BDC_OKCODE' '=ENTR'.
ENDIF.
LOOP AT IT_LGART INTO WA_LGART FROM X TO X.
CONCATENATE 'Q0008-LGART( ' CNT ')' INTO FLD.
PERFORM BDC_FIELD USING FLD WA_LGART-LGA01.
ENDLOOP.
LOOP AT IT_BETRG INTO WA_BETRG FROM X TO X.
CONCATENATE 'Q0008-BETRG( ' CNT ')' INTO FLD.
PERFORM BDC_FIELD USING FLD WA_BETRG-BET01.
ENDLOOP.
LOOP AT IT_ANZHL INTO WA_ANZHL FROM X TO X.
CONCATENATE 'Q0008-ANZHL( ' CNT ')' INTO FLD.
PERFORM BDC_FIELD USING FLD WA_ANZHL-ANZ01.
ENDLOOP.
X = X + 1.
CNT = CNT + 1.
ENDDO.
CALL TRANSACTION 'PA30' USING IT_BDCDATA MODE 'A' UPDATE 'A' MESSAGES INTO IT_BDCMSGCOLL.
LOOP AT IT_BDCMSGCOLL INTO WA_BDCMSGCOLL.
CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
ID = WA_BDCMSGCOLL-MSGID
LANG = SY-LANGU
NO = WA_BDCMSGCOLL-MSGNR
V1 = WA_BDCMSGCOLL-MSGV1
V2 = WA_BDCMSGCOLL-MSGV2
V3 = WA_BDCMSGCOLL-MSGV3
V4 = WA_BDCMSGCOLL-MSGV4
IMPORTING
MSG = V_MSG.
IF SY-SUBRC EQ 0.
COUNT = COUNT + 1.
WA_ERROR-RECORDS = COUNT.
WA_ERROR-MESSAGE = V_MSG.
APPEND WA_ERROR TO IT_ERROR.
ENDIF.
ENDLOOP.
ENDLOOP.
ENDFORM. " PROCESS_DATA
*&---------------------------------------------------------------------*
*& Form DISPLAY_ERRORS
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM DISPLAY_ERRORS .
WA_FCAT-FIELDNAME = 'RECORDS'.
WA_FCAT-SELTEXT_M = 'S.NO'.
WA_FCAT-OUTPUTLEN = '5'.
APPEND WA_FCAT TO IT_FCAT.
WA_FCAT-FIELDNAME = 'MESSAGE'.
WA_FCAT-SELTEXT_M = 'STATUS'.
WA_FCAT-OUTPUTLEN = '100'.
APPEND WA_FCAT TO IT_FCAT.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
IT_FIELDCAT = IT_FCAT
TABLES
T_OUTTAB = IT_ERROR.
ENDFORM. " DISPLAY_ERRORS
FORM BDC_DYNPRO USING PROG SCREEN.
CLEAR WA_BDCDATA.
WA_BDCDATA-PROGRAM = PROG.
WA_BDCDATA-DYNPRO = SCREEN.
WA_BDCDATA-DYNBEGIN = 'X'.
APPEND WA_BDCDATA TO IT_BDCDATA.
ENDFORM. "BDC_DYNPRO
*----------------------------------------------------------------------*
* Insert field *
*----------------------------------------------------------------------*
FORM BDC_FIELD USING FIELD VALUE.
CLEAR WA_BDCDATA.
WA_BDCDATA-FNAM = FIELD.
WA_BDCDATA-FVAL = VALUE.
APPEND WA_BDCDATA TO IT_BDCDATA.
ENDFORM.
Hi Seema
The way to make the view cluster show in display mode only is to change all the relevant maintenance view in "read only" mode, this can be done in the definition of maintenance view in SE11(see the below picture).
Then in the view cluster, the display/change button, new entry and etc will not be showed(see the below picture).
Hope this will solve your problem although it's long time ago you submit the question and maybe this will help others have the same issue and will help them.
Regards
Felix
Dear All,
Incident management in our solution manager is configured as per PCOE standard for SAP Partners.
In this, an individual user can raise message, send it to SAP, etc.
However we have a requirement from one of our customer that they wish to see & follow-up the incidents created by their team members as well.
So we are exploring at opportunities if it is possible that all staff belonging to 1 customer can see all incidents raised for this customer, and not the messages raised by other.
We have already tried to assign the persons as "Responsible for"; however this does not work as expected.
Can you please let me know, if this has been successfully configured and tested by any one?
Thank you.
Warm Regards,
Shilpa
Hello Jepoy,
Tcode KKBC_ORD might be useful for you to get this information.If you need tables then :
Try Tables
AUFK and PMCO
Try function modules
IBAPI_ALM_ORDERCOSTS_READ
K_KKB_KKBCS_CO_OBJECT_READ
Also see this link:
Best of luck
KJogeswaraRao
Hello experts,
Sorry I didn't explain it clearly before.
Actually the lower case action in the function definition was uploaded by text file(not manually input). And now every time I open this function in NWBC and try to save, it will show the "duplicate action" error message. So I have to remove either lower case one or upper case one, and save again. After the save, the deleted one will just come back.. And next time I open this function, I have to remove it again.. It's very annoying...
Jawahar, it's user security related, as shown in the attachment.
How to book the latest SAP BODS Certification exam?
Hi Ricardo
The code that I provided above was for the custom adapter module GetMultiAnexoXml2 that was shown in your module screenshot. It's just to change the content type for attachments to application/xml as you requested for, and it's not applicable for Java mapping.
Not sure what is your design - what is being done in module and what is being done in Java mapping.
Anyway, had a look at your code and here are some of my comments:-
i) itAtt not defined anywhere
ii) attachId is initialized to blank and not updated, so the condition attachId.length > 0 will never be true.
Rgds
Eng Swee
Leandro / Karen,
Recentemente recebi a solicitação de um cliente para considerar justamente modificações de CFOP decorrentes de CC-e no Livro Fiscal (report standard no SAP), pois este report é usado para confrontar com o SPED "oficial" (aplicação de terceiros), onde eles podem fazer tais manipulações.
Após muita pesquisa e troca de ideias, chegamos num acordo de que, conforme mencionado no guia do EFD, o que deve ser reportado é o CFOP após a CC-e.
Aceitei fazer isso considerando:
a) O documento legal não é a NF no SAP, mas o XML que foi gerado a partir dela.
b) O SAP permite realizar alterações de NF-es de entrada (manual) devido à necessidade de alterar a data de entrada da mercadoria para processos em que a data só é conhecida após a emissão (vide nota 1370016 - NFe: Posting date change for manual incoming NFe).
Se usássemos a J1B2N, haveria a tentação do usuário alterar outros dados que não deveriam ser alterados (e que não podemos travar, pois se a NF não foi autorizada ainda, os dados podem ser alterados normalmente, e não existe controle de tela que leve em consideração se o doc foi autorizado ou não), aém de que só funcionaria para NF-e de entrada...
Por conta disso criamos uma transação Z para simplesmente fazer um update de determinados campos, como o CFOP, e por estar então atualizado na tabela standard, o livro fiscal terá a informação correta e qualquer outro programa que leia as tabelas standard terá a informação "vigente" - para evitar confusões, as modificações ficam registradas no log de modificação da NF, também para comprovar em eventual fiscalização de que a alteração está conforme a CC-e.
Espero ter dado mais algumas ideias para considerar.
Abraços,
Eduardo Hartmann
Dear Pavan, Thank for the advise. We do not use class CL_ICF_SYSTEM_LOGIN. Our system is pure SAP Enterprise Portal. Please advise. Regards Yansen
hi Bobby,
Yes, but it doesn't always mean that the document in ECC was deleted. There could be cases where the document exists in ECC and GTS. But the linkage/reference is missing in GTS.
So, basically the reorganization is to identify the list of documents in GTS which doesn't have a reference/linkage to a document in feeder system. Once you have the list of documents in GTS, you can delete those customs documents here and retransfer the corresponding document from feeder system(if the problem was with linkage). If the case was the feeder system doc deleted, you can recreate the same and customs document will be created in GTS automatically.
Regards
Dhilipan
Hi Markus,UIrich,
Thanks for your replies and sorry for my late response.
Because of some internal resource restrictions and unclear information I had at that time, I asked this question. And now, it is clear that we will have the CC within our intranet.
Best Regards,
Iris
Hi,
Please elaborate further.
Regards,
Tejas
Hi Prasant,
The thing you are talking is by using the table GRFNVNOTIFYMSG where we can create custom message class, for the custom document objects we create. but what i am talking is the variables like " LINK_GET_APPROVERS", which we use in document objects. The link value being saved in the variable is a different link of the screen one then what i expect.
correct me if i am wrong.
When you use comment you have to manually set the position of the comment and the fields, that error means that you have in some place an overlapping of two element.
And also you have to declare the text in the event AT SELECTION-SCREEN OUTPUT.
This is the source code working.
SELECTION-SCREEN BEGIN OF BLOCK param WITH FRAME TITLE frame.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(10) scr_pnam FOR FIELD lv_name.
PARAMETERS: lv_name TYPE SPFPFLPAR-PARNAME DEFAULT 'rdisp/btctime'.
SELECTION-SCREEN COMMENT 60(10) scr_pval FOR FIELD lv_value.
PARAMETERS: lv_value TYPE spfpflpar-pvalue VALUE CHECK OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK param.
AT SELECTION-SCREEN OUTPUT.
frame = 'プロファイルパラメータ更新'.
scr_pnam = 'パラメータ名'.
scr_pval = 'パラメータ値'.
Regards
What is process of transfer finished material to ware house(FG Store).
What are the T.codes and what are the movement types to transfer the finishe material to ware house.
please help me out.
Hi,
In case you are using version ECC 5.00 or 6.00 or above SAP by default shows these balance. This will happen only n case you have carried out the carry forward activity for that particular vendor. In case you have not carried out the carry forward activity it would have not shown 19000.
In case you are doing carry forward activity for one vendor and do a test case wherein don't do carry forward activity for the vendor and other things same as vendor ABC
Hope, your query has been answered else revert.
Regards,
Tejas
Hi gita,
Replace
SELECTION-SCREEN COMMENT 50(10) scr_pval FOR FIELD lv_value.
with
SELECTION-SCREEN COMMENT 79(10) scr_pval FOR FIELD lv_value.
The specified offset 79 is maximum large.
Regards.