Академический Документы
Профессиональный Документы
Культура Документы
Find out the material number for corresponding Customer Material Number
In WE19, Remove the trailing space for the customer material character for the
identified material.
Repeat the process for all materials that have trailing NON-ASCII characters.
Get the new IDoc number and send it to EDI team for confirmation for transmission
from their end.
Last step is to follow up with Master data team to delete the special characters from
the source.
Failure due to invalid date update ( Where date format is wrong /12/23/0123
Failure due to memory overflow ( Most Frequent One )
We convert the trigger to C status and reach out to user who updated the
agreement.
When an AGR or MBL job fails with no details in the job log about the failure, we
have seen that this is due to memory overflows in the batch job.
For AGR records, this is due to A804 and A807 condition table triggers. In this case,
we reset the failed records and reprocess the records for A804 and A807 manually
in blocks of 50 records each.
Pull up the in process records from the AGR table with the Job Name and Job ID
Sort the Excel by the TABNAME column to identify the records for A804 and A807
that need to be processed manually.
Reprocess the A804 and A807 records by GUID in blocks of 50 using the program
ZMOTC_BATCH_UPD_AGR.
Step 2
Get the End time of the job to go through ST22 and narrowing down the search.
Step 3
Go to TCode: ST22, Give the time slow where the job failed. (Like in above case, job
failed at 03:00 I gave 02:59:00 03:01:00 in ST22 criteria)
Click on Start
Step 4
Double click on Error Analysis and search for MARA
Step 5
Get the records from ZMTOTC_PRCHGEVTS table in B status by giving job name and
job number as parameter.
Extract the records into one excel, and look for the records containing that
particular material that is being shown in Dumps. In this particular case, there were
3 records for this material. Look for the change that generated this event.
In above case, one condition record was added (As there is no old value mentioned)
Go to KONH table to get more details on this specific condition record number,.
KONH table pointing to Table A016 and condition type ZB01 ( Which is a STS
condition type for gross price )
Step 6
Go to table A016 and put the Condition Record number to get purchasing requisition
and other details required.
Step 7
Go to TCode MEK3 (Condition Record Display)
Gross Price added as $0.00 for Material #M6160-2 causing issues to PCH as
well as PQ Jobs ( Note : If we try to run PQ for this material with UoM as CS, PQ
job will also fail giving a dump )
Step 8
Next Steps: To Process records other than this particular record.
Apart from the records containing erroneous material, Convert everything else ( all
other GUIDs from this particular job to status A )
Program Name: ZMOTC_RESET_PCH_TABLES
These records will be picked up by normal PCE Cyclic jobs and look for status C
once these are processed.
Need an exception mechanism to avoid the failure while inserting the records
in ZMTOTC_PCH_DEL table.
CPA_IL Execution
Purpose: When the order changes to incomplete after getting invoiced due
to variation in tolerance of the expected price and this scenario mainly occurs
when the customer is unavoidable or to be given the expected price in view
of further the business requirements. These orders needed to be released .
The job(Membership job) was cancelled at step 231 and hence guids has to be
extracted from step 232.
Click GOTO
Click variant
From this screen the guids are transported to excel sheet and the process is
repeated until GUIDs of all the steps(232-243) are extracted and saved in a excel
file.
Then in sm36 the background job is created by giving the job name and going to
step we give the program name and variant name and then 51 GUIDs of one step
is copied and pasted from the excel sheet on to the edit variant screen where there
is a field for GUIDs.
The same process is repeated by copying the job and editing its name and changing
the guids until all the guids are processed.
Go To VBRP table after extracting all the billing documents from the child job which
got failed due to Profitability segment missing.
Then copy and paste all the billing documents that was extracted in the VBRP table.
And give the selection criteria for the Profitability segment as = and execute it.
The billing document which has no profitability segment will be shown and the
billing document is noted down.
The billing document is then excluded in all the billing extract job and the accrual
job.
Then we exclude the billing document from the extracted billing documents and the
remaining all documents are copied and pasted as variant in the new child job that
was copied from the failed job.
Now the new copied job is released
Copy the Child job and exclude the billing ( From Subsequent Billing
extract jobs as well )
After the job gets completed, unblock the failed IP Create job
Compares Line Items that we have in Recon and In the file ( We compare
Dollar value as well )
We send Idocs to PI and receive file from PI via MFT
We receive one log file as well along with the files
This log file contains summary of file name, line count and amount.
It creates triggers for loading the files in Hadoop.
Job
Program Name
Variant
Components of Variants
Transmission Medium
Weve 2 options here, 1 for validating CB CSV File, another one is for
marketing trace file, Market trace file validation will normally run during
month-end, however if there is a request in between for ad-hoc file
transmission request, well need to schedule ad-hoc marketing trace file
validation job for pushing the files to Hadoop.
Manual Run
Manual run is used whenever there is failure and weve couple of vendors
pending to be validated, well have to re-run the job for pending vendors by
hardcoding the vendors in vendor selection box.
Ad-hoc Run
This option is used for running on-demand validation job (For catering to our
ad-hoc sales trace requests ), There needs to be a .done file before we can
run any ad-hoc validation job.
We need process date as well as Sourcing vendor for running ad-hoc job
Sleep time
Program looks for updates on log file, if log file is not updated for 30 mins , it
assumes that log file has been received completely and it will start
comparing the log file contents against Recon entries. Sleep Time is the
interval on which program will check for update timestamp on log file. For
example : In the screenshot weve 10 minutes ( 600 secs ), This means that
system will check the timestamp on log file every 10 minutes, it cant be very
low as it will keep the program busy in looking through log file in very short
intervals of time.
As shown In screenshot
Sub-directory MSTR_audit_files
For Marketing trace file validation
Sub-directory CBClaim_audit_files
For CB CSV File Validation
CBClaim
Signifies that file is CB CSV and Not Market Trace CSV
502312
ZT Vendor
0000600221
PI Vendor
0000302311
VN (Sourcing Vendor)
P
Signifies that it is paid file, that is vendor can see it on portal and download it, If
value is U, CAH Team will send the pdf file to vendor.
20151207
Is the process date for which file was generated
20151208
Is the date when file was created, it is appended dynamically by PI while generation
of the file.
7
Is the line count
5372.00
Total Extended CB Amount
.wip
.log file is converted to .wip during the processing time
.adh
.adh file is the temporary file extension used during processing of ad-hoc validation.
.done
.log file is converted to .done file once processing is complete and
successful.
.mis and .cor
These files are created only in case of failures.
.mis file will contain vendor list that missed the validation (Either these vendors has
less number of lines than expected or have duplicate lines )
.cor file will contain the vendor list for which validation passed successfully.
Once all IDocs are processed from SM58, well receive one supplemental .log file,
and from here steps will be same as mentioned above.
Trigger Path
It is a plain text file that has the same file name as the one that needs to move into
Hadoop. It will have validated as the content.