Reg: Posting Document creation issue

Dear experts,
we have hired 20 employees in a month from start date 01.01.2011, with updating all the personal and payroll records. We have run the payroll for all employees, which has updated all payroll results. When we came across the posting part, among 20 employees only 19 employees gets executed and for 1 single employee the posting documtne didnt get created.
Please help us in the solving following issue.
With Regrads
Chandan Maity

Hi Chandan,
Please go to PPMOD and make sure that this employee is linked to a group via this feature (cost center vs fields are maintained)
Please also make sure that employees payroll results reside in PC_PAYRESULT t-code without errors.
Regards,
Dilek

Similar Messages

Reg: Sales document creation

Hi Abapers,
As i am new to SD Module, would like to get some ideas from your end. My requirement is to create a sales order using Programming. After creation of sales order it should post to finance. Could anyone help me how this can be done.

REPORT ZSALESORDER.
* Parameters
* Sales document type
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
* Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
* Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d .
SELECTION-SCREEN END OF LINE.
* Complete Deliver
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text10 FOR FIELD p_autlf.
PARAMETERS: p_autlf TYPE autlf DEFAULT 'X'.
SELECTION-SCREEN END OF LINE.
* Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                         WITH HEADER LINE.
DATA: lt_schedules_ink    TYPE STANDARD TABLE OF bapisdhead1
                         WITH HEADER LINE.
* Initialization.
INITIALIZATION.
v_text   = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
v_text10 = 'Complete delivery'.
* Start-of-selection.
START-OF-SELECTION.
* Header data
* Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
* Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
* Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
* Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
*Complete delivery
    header-COMPL_DLV = p_autlf.
    header-COMPL_DLV = 'X'.
* Partner data
* Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
* Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
* ITEM DATA
itemx-updateflag = 'I'.
* Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
* Material
item-material = p_matnr.
itemx-material = 'X'.
* Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
* Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
* item category
itemx-ITEM_CATEG = 'X'.
APPEND item.
APPEND itemx.
*   ITEM DATA
itemx-updateflag = 'I'.
* Line item number.
item-itm_number = '000020'.
itemx-itm_number = 'X'.
* Material
item-material = p_matnr.
itemx-material = 'X'.
* Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
* Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
*   Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
*   Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
*   Fill schedule lines
lt_schedules_in-itm_number = '000020'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
*   Fill schedule line flags
lt_schedules_inx-itm_number = '000020'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
* Call the BAPI to create the sales order.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
       EXPORTING
            sales_header_in     = header
            sales_header_inx    = headerx
       IMPORTING
            salesdocument_ex    = v_vbeln
       TABLES
            return              = return
            sales_items_in      = item
            sales_items_inx     = itemx
            sales_schedules_in = lt_schedules_in
            sales_schedules_inx = lt_schedules_inx
            sales_partners      = partner.
* Check the return table.
LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
ELSE.
* Commit the work.
    COMMIT WORK AND WAIT.
    WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.
Code Formatted by: Alvaro Tejada Galindo on Dec 26, 2008 10:58 AM

Billing document creation issue

Hi,
I created an intercompany contract when i goto VF01 and execute it log is generated and it says
"000010 Error no WBS billing element found while substituting WBS element*******"
What should i do now?

Dear friend,
For intercompany there is no need for WBS element. Kindly make it an optional entry for your sales order level.
Or else consult with your PS consultant who has created this WBS element.
regards,
Sudhir

Auto print of Goods Issue/Transfer Posting Documents by Movement type

Hi,
We have created two different output types to print the layout's of Goods Issue/Transfer Posting Documents.
The requirement is to default the message in the document by movement type (key combination)
Meaning if it is 201 it should populate GI output type
If it is 313 it should populate TP output type.
we do not have any standard key combination (NACR) by movement type wise.
Any alternative way of meeting this requirement?
Thanks
Regards
Ram

Hello Kevin,
I donu2019t think it is necessary to use a user exit to keep the Material B (that is transferred from Material A) in the same bin.
This can be controlled in the customizing: indicator Post to same bin, that can be set in the WM Movement type (V_T333-KZUAP) and in the Storage type (V_T3010-KZUAP).
Now I donu2019t know your business process but I am surprised that Material B requires more space than Material A since it is u2018bornu2019 by means of a transfer posting and not a production or packing step that makes it bigger in terms of capacity required.
A workaround for this could be to transfer (LT10) Material A first to a separate Storage type (with the Post to same bin-flag set) that has no Capacity check and after the 309 posting transfer it back into the warehouse with LT10.
Success and thanks beforehand for any credits!
Kind regards,
Bart

Posting Document not created (export data missing)

We are working on ECC 6.0 and during creation of Cancellation Billing document type IVS for the Intercompany billing, the document did not create Accounting document giving the Posting status as G - Posting document not created (export data missing). However checked the Foreign trade data and the system states that Foreign trade is complete.
Can any one suggest the solution for this?
Thanks.

Hello Mohammad,
About this issue, the incompletion of this cancellation document
arises might because the reference delivery has been archived/deleted.
This is likely due to your current copy control settings (VTFL).
If you have set ' ', in the export determination field this means that
there is a common 'exnum' key between the delivery and billing documents
LIKP-EXNUM & VBRK-EXNUM are the same.
The result of deleting the delivery is that you also delete the FT data
for the delivery, Because the billing document and delivery share the
same foreign trade table entries, you have in effect deleted the FT data
of the billing document too. This would most likely go unnoticed but if
you then cancel the invoice the system has no FT to copy into the new
cancellation billing document, which leads to this issue.
Firstly you should set the export determination flag in the copy control
of the delivery & billing documents. This will avoid this issue in the
future. Set it to to 'A' or 'B' depending on your requirements.
For the incomplete cancellation billing document, you could use userexit to
set it as complete:
You can use transaction CMOD.
Create a project for example FT project button create short text: ....
drop button Enhancement assignment & save use for example local object.
Use the F4-help for Enhancement and look for V50EPROP.
Drop button Components:
here you will find EXIT_SAPLV50E_005 and EXIT_SAPLV50E_006
In the userexits doubleclick on the includes ZXV50U05 and ZXV50U06
The coding in the userexits should be: C_COMPLETE = 'X'.
Afterwards activate generate ... and save.
The development class is VEI.
Please also check note 118573 which explains the FT user exits.
Regards,
Alex

I am facing problem document creation the error is Message no. 3G103

i am facing problem document creation the error is Message no. 3G103

Dear Satish,
Usually this error is due to a wrong customizing.
Go through note 1594322 and 179655 will help you to make an analysis of this issue, you should created an excel file for each wage type which should be posted as it is showed in the note.
1594322 Error message 3G103 in RPCIPE00 & RPCIPE01 'Posting balance is
not cleared' 179655 RPCIPE00:Rejectn, employee w.posting bal.not clrd
Best Regards,
Deepak.

Issue while posting using goods issue for delivery type NL

Hello Experts,
I have created an outbound delivery for an intra-company transfer (within same company code) between two plants. The delivery type in NL (replinishment delivery)
When i am trying to post the goods issue from supplying plant, I am getting following error
"Account type K is not defined for document type WL".
Delivery type NL should not be used to issue stock to vendor but I am not issuing it to any external vendor , issuing the stokc only to a receiving plant.
Please help to understand why i am getting this error.
Regards,
Nish.

Hi,
If you are doing an STO Scenario, Check whether you have created the supplying plant as a vendor.
The Vendor Account group should be plants.
Also check whether you have given the plant in the vendor master Purchasing Data - Extras tab in the menu click on add purchasing data & check.
If you haven't assigned this, do the same & create a fresh STO & check.
Hope it will work.
Thanks & Regards,

Photoshop CS4 new document dialog issue...

http://img50.imageshack.us/img50/7835/optionpu6.gif
Can this Photoshop CS4 new document dialog issue be improved? Info in the pic.

there's a feature request section at the top of the fourm allen. these kinds of posts should be done in there, so the programmers and engineers at adobe have them all in one place.

Reg: Posting of payroll for new employee joined

Dear Expert,
We have hired a new employee, maintained all infotypes including 0009 also. We are facing problem once the payroll have run. his RT table have got updated, cluster result have been updated. but when we go for posting purpose, that employee doesn't gets selected for posting run also. the system is not at all selecting the employee for any document creation.
with regards
sumoy maity

HI,
Tcode - PC00_M99_CIPE
Enter Employee Code
Select the tick - display Log
Do live run
This will show you the run number if the employee data has already been selected for actual run.
You can use this Run number for further processing.
Hope this helps.
Param.

Posting Document num not captured in BDC message table

I am working on a dataload program for Asset Transfer using tcode ABUMN. If I run ABUMN online, it will give me the message saying, 'Asset Transaction posted with document no. xxxxxx' after saving the trx. However, I can't capture this message while running the Call Trx/BDX program.
I don't know why the message table is empty after a successful Call Transaction. If there is an error, it will capture it, but no meesage if the trx is successul. I thought the table will capture any message whether it is a 'S' or 'E' or 'W'. It works for other tcodes, but not for tcode ABUMN.
DATA: T_MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
" Batch Input Message table
call transaction C_TCODE using t_bdcdata
MODE P_MODE
UPDATE P_UPDATE
MESSAGES INTO T_MESSTAB
CAll Transcation is a standard code, so there is need to specify what types of message should be captured.
I remember seeing some threads about the empty message table, and they suggest to use Parameter Id to capture the posting document #. I tried par id ' BLN' and still not able to see anything there.!!
Can anyone help?
Thank you in advance for any help. Greatly appreciated.

Hi,
I have come across with the same issue with transaction CS01. I have done it in a round away . I find an userexit after save , and export the document number to memory and after the call transaction import the document number from memory and updated the BDCMSGCOLL table.
May this info will be helpful to you.
a®

Posting multiple goods issues against the same delivery

Hello gurus,
We are a fashion apparel company using ECC 6.0 and would like to know if it is possible to post mutliple goods issues against the same delivery?
I will explain the business requirement.
- We create a stock transport order to deliver 400 units of merchandise to on or our retail stores (STO is created and processed to a delivery).
- This information is passed down to our warehouse management system (which is not SAP)
- Our warehouse management system has the ability to split a delivery into multiple shipment when needed. For example, our warehouse may only be able to complete 250 units for our morning shipment and will therefore pick, pack and post this. This will feed back into SAP and process a 641 movement so that the units now show as "in transit". This is needed so that our stores can process the ASN and move the units into their inventory when they receive the merchandise later that day.
- During the afternoon, our warehouse will process the remaining 150 units and will ship this to our store later in the evening or next day.
Currently, we are not able to process another goods issue against a delivery as we close out the delivery during the first goods issue. We would prefer not to have to generate a new delivery for our DC and let them continue to process against the same delivery, but we are unsure how to configure this.
Any help or guideance would be extremely appreciated
Thanks in advance

Hi RJ,
First of all sorry to write such a lengthy reply,In one line if i want to summerize then it is not possible with standard SAP however we can achieve this by writing some piece of code in both the system
AS - IS
               Business process
          From business process point of view you are right that once the pick & pack is in process it is not advisable to create a new delivery document for balance quantity and share the same with WMS as then they have to create a new document in WMS and start picking based on that rather then the old delivery document number. if i am in your position then i can give a thought like this
e.g.
Delivery                                                  - 100 Unit
Shipment confirmation from WMS            -   60 Unit
Change in delievry quanity / Pick qty        -   60 Unit
Invoice from SAP                                    -   60 Unit
Second confirmation from WMS                          -   40 Unit
Change in the existing delivery quantity                -   Now here we have two option either
1) Change the delivery quantity / Pick qty to (60+40) =100 or
2) Remove the 60 and update 40 as delivery and pick quantity
Pros & Cons
if you will select option 1 then furhter invoice will happen for 100 unit which is incorrect as physically you are shipping only 40 unit
if you are selecting option 2 then the document flow is incorrect as you don't have history(in SAP) for the 60 unit which was shipped earlier
Solution ::
so in my opinion the best option is to create a seperate delivery document (store the old delviery number in one of the field of the new delivery and pass the same to custom segment of the IDoc) transmit the IDoc to WMS write the validation logic in WMS
Find the record with old deliver number in the WMS system, check the status whether it is active or inactive
if it is acitive Validate the Material + qty with the WMS record(Material + balance quantity) if both are same then pass the new deliery number to custom field of the WMS table
At the time of confirming back to the SAP, Write a piece of code in SAP that if the incoming idoc custom field(new delivery number) field is populated then ignore the orignal document number and post the document using the new delivery document number
Hope this help

Post a good issue against an outbound delivery with movement type 601 K

Hello,
according to my business scenario I need to manage the stock of different vendors into the client's location (plant) at storage location level and I need to post the good issue against an outbound delivery to decrease the stock level.
Since the owner of the goods isn't my client the item is managed only at quantity level (not value) so I'm not interesed in the accounting document.
To do it I'm using the functionality related to the vendor consignment stock but I'm not able to post the good issue against an outbound delivery using the movemement type 601 and the special stock indicator equal to K.
In particular I've tried in two different ways:
- setup the consignment stock indicator (= K) into the sales item category, but when I post the goods issue the system is not able to find out the right vendor
- to create a stock determination rule instead of the setting previous described, but the system display an error message (Fld selectn for mvmt type 601 / acct L534200770 differs for Cost center (010) ) even if the accouting is not relevant in my scenario
Can you suggest me how the system has to be setup in order to cover my requirements?
Thanks in advance,
Alessandro

Hi,
Please clarrify which material type you are using in this scenario? I suggest you to use material type UNBW (no value updation will be there) and create a material master. Use special stock indicator K. Proceed with 601K to do GI. Hope it works. Thanking you.

Error when posting an goods issue of movement type 501: order not contain

I tried to post an goods issue of movment type 501 to a stock transport order. But I get the error as below.
Document 4500000130 does not contain any selectable items
Message no. M7 064
Diagnosis
The document or item entered cannot be adopted.
Possible reasons for this are:
The document items have already been processed
(Suggest zero lines indicator set?).
the document items have been deleted or are blocked.
the document items have been created for a different plant.
(for reservations only) movements are not yet allowed for the reservation items.
(for reservations only) the document items are retrograde components of the order. These are posted using the order confirmations.
The document is an R/2 document.
Procedure
Make sure your entries are correct.
If the system has already processed the total quantity, you can set the Suggest zero lines indicator. The system will suggest the quantity zero for the items that have already been processed.
If you have entered a particular item, cancel the item. If you do not enter an item, the system searches all of the open items in the document.
If the document is a purchase order, production order or a reservation, you can enter search criteria in the dialog box.
You access the dialog box by choosing the menu option Enter with reference on the initial screen.
If the document is an R/2 document, you have to cancel it manually by entering the reversal movement type.
How can I proceed to post?
Thanks,
Eda

Hi
Go to T.code MB1A, enter the required movement type, Plant and storage location and then click,
The push button of Reservation on the tool bar for refereing the reservation or
The push button of order on the tool bar for refereing the Production order.
Cheers
Kris

How to get material's last posting date of issuing to production order?

Hi,
In my scenario, I need to get material's last posting date of issuing to production order (e.g. mov. typ. 261).
I tried to select the material documents whose movement type is 261, and restrict the posting date from month to month each time, until the first material document is selected.
But this method seems quite inefficient.
What kind of algorithm is more effient to do this?
Thanks
Wesley

Hi,
select max( budat )
from mkpf
into gv_budat
where mblnr in ( select mblnr
                     from aufm
                    where aufnr = gv_aufnr "(Prod. Order)
                        and matnr = gv_matnr "(Issued Material)
                        and bwart = '261' ).
Edited by: Azeem Ahmed Matte on Mar 12, 2010 12:33 PM

Not able to post document using BAPI_ACC_GL_POSTING_POST

Hi all,
While trying to post documents in FB60 using BAPI_ACC_GL_POSTING_POST we are getting error Account not assigned to company code. But we are able to post documents manually using the same account and company code. Couls any one help me out to resolve this issue.
Thanks & Regards,
Neela.

This is complete procedure to use 'BAPI_ACC_DOCUMENT_POST'. It can be used for GL, AR or AP documents.
Step 1:
For Header information, fill u201CDocumentHeaderu201D structure as:
obj_type = 'BKPFF'
obj_key = '$'
obj_sys = CONCATENATE syst-sysid 'CLNT' syst-mandt
bus_act = 'RFBU'
username = syst-uname .
comp_code = Company Code
doc_date = Document Date
pstng_date = Posting Date
doc_type = Document Type like AB, SA.
ref_doc_no = Reference Document
To populate the line item data, fill internal table u201Caccountglu201D or u201Caccountpayableu201D or u201Caccountreceivableu201D as:
itemno_acc = Line Number (like 10,20)
gl_account = GL Account Code (For GL Line Items only)
vendor_no = Vendor Number (For AP Line Items only)
customer   = Customer Number (For AR Line Items only)
acct_type = 'S' or u2018Ku2019 or u2018Du2019. (GL = u2018Su2019, AP = u2018Ku2019, AR = u2018Du2019)
costcenter = Cost Center
orderid    = Internal Order
tax_code   = Tax Code
item_text = Item Text
quantity   = Quantity
base_uom   = Unit for Quantity
Note:
u2022 Separate internal tables should be created for GL lines, AP Lines and AR Lines.
u2022 If posting GL line items then only u201Caccountglu201D internal table should be filled.
u2022 If posting AP document then GL lines should be filled in table u201Caccountglu201D and Vendor lines should be filled in table u201Caccountpayableu201D.
u2022 If posting AR document then GL lines should be filled in table u201Caccountglu201D and Customer lines should be filled in table u201Caccountreceivableu201D.
u2022 Extension of each line of u201Caccountglu201D, u201Caccountpayableu201D and u201Caccountreceivableu201D must be there in u201Ccurrencyamountu201D.
To populate the amount, fill u201Ccurrencyamountu201D structure as:
itemno_acc   = Line Number (like 10,20, but pair of u201Caccountglu201D line)
amt_doccur = Amount {Credit amount should be with sign
currency = Currency
Step 2:
CALL FUNCTION 'BAPI_ACC_DOCUMENT_POST'
EXPORTING
    documentheader = st_documentheader
IMPORTING
    obj_key        = w_objkey
TABLES
    accountgl      = i_gl {GL Line Items}
    accountpayable = i_ap {AP Line Items
    accountreceivable = i_ar {AR Line Items}
    currencyamount = i_amt {Amount of all above}
    return = i_bapiret. {Return messages}

Reg: Posting Document creation issue

Similar Messages

Maybe you are looking for